jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Collin" <m...@ardescosolutions.com>
Subject RE: Publishing to Maven Central
Date Thu, 19 Jan 2012 09:13:30 GMT
Oh this has highlighted another difference between the implementation I
supplied and your one, I have a POM named ApacheJMeter_reports and you have
one named ApacheJMeter_report.  If you do want to use the one I supplied
you'll need to take the s off the name to make it match your current POM.

-----Original Message-----
From: Mark Collin [mailto:mark@ardescosolutions.com] 
Sent: 19 January 2012 09:09
To: dev@jmeter.apache.org
Subject: RE: Publishing to Maven Central

OK I have tried using the 2.6-SNAPSHOT at
https://repository.apache.org/content/repositories/snapshots/ and I get the
following dependency issues:

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.bouncycastle:bcmail-jdk15:jar:$(bcmail.version}

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.bouncycastle
-DartifactId=bcmail-jdk15 -Dversion=$(bcmail.version} -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
      mvn deploy:deploy-file -DgroupId=org.bouncycastle
-DartifactId=bcmail-jdk15 -Dversion=$(bcmail.version} -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.jmeter:maven-jmeter-plugin:maven-plugin:SNAPSHOT
        2) org.apache.jmeter:ApacheJMeter_core:jar:2.6-SNAPSHOT
        3) org.bouncycastle:bcmail-jdk15:jar:$(bcmail.version}

2) maven-plugins:maven-cobertura-plugin:plugin:1.3

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=maven-plugins
-DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
      mvn deploy:deploy-file -DgroupId=maven-plugins
-DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.jmeter:maven-jmeter-plugin:maven-plugin:SNAPSHOT
        2) org.apache.jmeter:ApacheJMeter_core:jar:2.6-SNAPSHOT
        3) org.jdom:jdom:jar:1.1.2
        4) jaxen:jaxen:jar:1.1.3
        5) maven-plugins:maven-cobertura-plugin:plugin:1.3

3) maven-plugins:maven-findbugs-plugin:plugin:1.3.1

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=maven-plugins
-DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
      mvn deploy:deploy-file -DgroupId=maven-plugins
-DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.jmeter:maven-jmeter-plugin:maven-plugin:SNAPSHOT
        2) org.apache.jmeter:ApacheJMeter_core:jar:2.6-SNAPSHOT
        3) org.jdom:jdom:jar:1.1.2
        4) jaxen:jaxen:jar:1.1.3
        5) maven-plugins:maven-findbugs-plugin:plugin:1.3.1

4) org.apache.jmeter:ApacheJMeter_mail:jar:2.6-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.apache.jmeter
-DartifactId=ApacheJMeter_mail -Dversion=2.6-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
      mvn deploy:deploy-file -DgroupId=org.apache.jmeter
-DartifactId=ApacheJMeter_mail -Dversion=2.6-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.jmeter:maven-jmeter-plugin:maven-plugin:SNAPSHOT
        2) org.apache.jmeter:ApacheJMeter_mail:jar:2.6-SNAPSHOT

----------
4 required artifacts are missing.

for artifact:
  org.apache.jmeter:maven-jmeter-plugin:maven-plugin:SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  Java maven repo
(https://repository.apache.org/content/repositories/snapshots/),
  Maven JMeter Repo
(http://ardesco.github.com/jmeter-maven-plugin/repository)



[INFO]
------------------------------------------------------------------------

Regards

Mark

> Sebb,
>
> There is a transitive dependency issue with JDOM pulling in jaxen 
> which by default tries to pull in some plugins that are not available:
>
> http://blog.cedarsoft.com/2011/12/fixing-maven-artifact-jaxen/
> http://jira.codehaus.org/browse/JAXEN-217
>
> This is fixed in the package I supplied yesterday by adding an 
> exclusion for jaxen.
>
> I have also added in a repo that has jchart 0.75 available, and one 
> for beanshell 2.0b5 (although checking just now I have missed the 
> dependency block for beanshell in the parent POM so it isn't actually 
> pulling beanshell down).
>
> I'll look at it in a bit more anger in a couple of hours to provide 
> some more useful feedback.
>
> Ant-contrib is used in the patch I have supplied to loop through a 
> couple of lists and add in an if/else block that will allow you to 
> choose if you want to add sources and javadoc jars when deploying, if 
> you don't want to do these things it isn't needed.
>
> Regards
>
> Mark
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: 18 January 2012 23:39
> To: dev@jmeter.apache.org
> Subject: Re: Publishing to Maven Central
>
> On 18 January 2012 22:45, Mark Collin <mark@ardescosolutions.com> wrote:
>> Uploaded a final version just now.
>>
>> I had to fix some transitive dependency problems that were not 
>> apparent until you tried to use the artifacts and I had one POM that 
>> was not correctly referencing ApacheJMeter_parent.
>>
>> The final version will also automatically download ant-contrib if you 
>> don't have it to make the whole process easier.
>
> I don't think we need the ant-contrib; so long as Maven is locally 
> installed it's possible to access it using Java.
>
> I recently committed an Ant script that uses this technique to upload 
> the jars (so far not source or javadoc).
>
>> Let me know if it needs any more tweaking.
>
> Have you seen the snapshots I uploaded?
> Do the poms work OK?
>
> If not, what needs to be fixed?
>
>> Regards
>>
>> Mark
>>
>> -----Original Message-----
>> From: Mark Collin [mailto:mark@ardescosolutions.com]
>> Sent: 18 January 2012 14:10
>> To: dev@jmeter.apache.org
>> Subject: RE: Publishing to Maven Central
>>
>> I was trying to find a way that would use a unified dependency list 
>> for both the ant build and the maven deploy.
>>
>> The path I have been going down is creating a dependency POM for doc, 
>> core and api and making them required dependencies of 
>> ApacheJMeter_parent.  I have then modified build.xml to use these 
>> dependencies instead of build.properties, but I'm running into issues 
>> with the existing classpath declaration in the build.xml because it 
>> doesn't just use all of the files in core, doc, or api.
>>
>> I'll upload what I currently have
>>
>>
>> -----Original Message-----
>> From: sebb [mailto:sebbaz@gmail.com]
>> Sent: 18 January 2012 12:41
>> To: dev@jmeter.apache.org
>> Subject: Re: Publishing to Maven Central
>>
>> On 18 January 2012 12:30, Mark Collin <mark@ardescosolutions.com> wrote:
>>> It looks like you have specified all of the dependencies in the 
>>> ApacheJMeter_parent pom.
>>>
>>> I thought you wanted a unified set of dependencies that are only 
>>> declared in one place.
>>
>> Ideally, yes, but that looks to be hard to do.
>> This approach should be enough to publish the jars and it's not to 
>> hard to maintain.
>> If it can be improved later, so much the better.
>>
>>> The code I have right now will deploy to a repo using ant to call 
>>> the mvn deploy command via an exec command.  It's working on Linux 
>>> and Windows and just requires you to have maven installed upon your
system.
>>
>> Does it use standard Ant?
>> Can you attach the file to the Bugzilla issue so I can try it?
>>
>>> I can add in the dependency list to the parent.pom and it will all 
>>> work
>> right now.
>>
>> Huh?
>> What's wrong with the existing dependency list in ApacheJMeter_parent 
>> pom?
>>
>>> -----Original Message-----
>>> From: sebb [mailto:sebbaz@gmail.com]
>>> Sent: 18 January 2012 10:56
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Publishing to Maven Central
>>>
>>> On 18 January 2012 06:35, Mark Collin <mark@ardescosolutions.com>
>>> wrote:
>>>> I'm in the progress of writing my second attempt at providing a 
>>>> working maven solution which you can see here:
>>>
>>> It looks to me like an Ant build script using Maven deploy, i.e.
>>> Maven is not used for building.
>>>
>>>> https://github.com/Ardesco/jmeter/tree/trunk/maven
>>>>
>>>> The sticking point I have at the moment is plugging in the 
>>>> dependencies, I have been looking at tweaking the existing ant 
>>>> script to use maven-ant-tasks, this is how far I have got (It 
>>>> doesn't
> work yet):
>>>>
>>>> https://github.com/Ardesco/jmeter/blob/trunk/build.xml
>>>>
>>>> Downloading the dependencies is trivial, however finding a nice way 
>>>> to specify individual jars for the classpaths and the release 
>>>> mechanism is not quite so tidy, the most sane way would seem to be 
>>>> a series of POM files to set the dependencies for each requirement 
>>>> but I'm not sure if that is changing the existing build process too
much.
>>>
>>> Ant does not care about the dependencies being distributed 
>>> accurately, so long as all the dependencies are present.
>>>
>>> AFAIK Maven need not either; if the parent depends on all the 3rd 
>>> party libs, then every JMeter jar can depend on the parent.
>>>
>>> Intra-module dependencies in JMeter are quite simple and don't 
>>> (generally must not) change.
>>>
>>>> Today I was planning on having a look at building some dependency 
>>>> POM's for the maven deploy on the fly from the build.properties as 
>>>> maybe a saner way to do things which will won't touch the existing 
>>>> build.xml at all, although I'm not that happy with this solution 
>>>> either
>
> --
> This message contains confidential information and is intended only 
> for the individual named. If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail. Please notify 
> the sender immediately by e-mail if you have received this e-mail by 
> mistake and delete this e-mail from your system. If you are not the 
> intended recipient you are notified that disclosing, copying, 
> distributing or taking any action in reliance on the contents of this 
> information is strictly prohibited.
>
> If you have received this email in error please notify 
> postmaster@ardescosolutions.com
> --
> This message contains confidential information and is intended only 
> for the individual named. If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail. Please notify 
> the sender immediately by e-mail if you have received this e-mail by 
> mistake and delete this e-mail from your system. If you are not the 
> intended recipient you are notified that disclosing, copying, 
> distributing or taking any action in reliance on the contents of this 
> information is strictly prohibited.
>
> If you have received this email in error please notify 
> postmaster@ardescosolutions.com
>


--
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.

If you have received this email in error please notify
postmaster@ardescosolutions.com
--
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.

If you have received this email in error please notify
postmaster@ardescosolutions.com

--
This message contains confidential information and is intended only for the individual named.
If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on the contents of
this information is strictly prohibited.

If you have received this email in error please notify postmaster@ardescosolutions.com

Mime
View raw message