Re: question on capabilities of AntRun plugin

[Cody zhang]

Hi,Jacob
Can you paste your code example?
Best Regards，
--Cody.Zhang


2010/8/27 Jacob Beard 

> Hi,
>
> I have question on the capabilities of the AntRun plugin. This example
> shows the Maven classpaths being copied into Ant properties, which are then
> used in Ant:
>
>
> http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
>
> I thougth it would be useful to reference these classpaths directly in Ant,
> rather than using the copied properties, and so I ran a series of tests.
> What I found was that the maven classpaths could be referenced, but only in
> the scope of the called target. When used outside of a target (in a taskdef,
> for example), an error is thrown. On the other hand, properties that are
> created in the Maven tasks element can be used both in and outside of the
> scope of the called target. This is using the ant task, with both
> inheritsAll and inheritsRefs set to true.
>
> I'm wondering if I'm correct in the above assessment of the capabilities of
> antrun. Can maven classpaths not be referenced directly, outside of the
> scope of the called ant task? If they cannot, what is the best way in Ant to
> read a classpath that has been read into a property back into a path
> element?
>
> Let me know. Thanks,
>
> Jake
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Change development version

[Anders Hammar]

Just a comment regarding your example. I'm assuming that the actual
"release" (the final one) will be 1.4, right? And that you're thinking that
you will be releasing some kind of milestone called 1.4-pre-1, right?
In that case, I would still call the development version 1.4-SNAPSHOT all
the way until you release the final 1.4 release. During the course, you
decide to release stable milestones (or whatever you want of call them, they
are maven releases anyway) such as 1.4-pre-1, 1.4-pre-2, etc. Then just cut
a release from the 1.4-SNAPSHOT lane that you give the version 1.4-pre-1.
The developement version continues to be called 1.4-SNAPSHOT after that.
Maybe someone else can comment on this approach, but I find it good as the
ones that want to use the latest snapshots don't have to worry about if they
should use 1.4-pre-1-SNAPSHOT, 1.4-pre-2-SNAPSHOT, or similar. They just
specify 1.4-SNAPSHOT and always get the latest from that lane. While the
ones that specifically want to use/try a milestone release use that version
(e.g. 1.4-pre-1).
Another benefit is that you don't have to decide on this milestone release
in advance (as you don't use their specific version number in the snapshot
version), but can cut them as you like. Maybe you cut them every night by
your CI, or every Sunday?

/Anders
On Thu, Aug 26, 2010 at 17:23, C. Benson Manica  wrote:

> What is the "proper" way to update the development version of a project
> (and
> its subprojects if any)?  Say a project is currently at 1.4-SNAPSHOT but I
> decide I want to mark it as 1.4-pre-1-SNAPSHOT - is there a way to do that
> without manually editing all the poms involved?
>
> --
> C. Benson Manica
> cbman...@gmail.com
>

Re: Is the archetype creation documentation confusing to anyone else?

[Hervé BOUTEMY]

true, I made bad copy/paste (and a few other english typos, as you can see).
Thanks for the report.

I fixed it, it should be available on the site in a few hours.

If you find other errors int he documentation, please open Jira issues. It's 
even better if you can propose a patch :)

Regards,

Hervé

Le vendredi 27 août 2010, lukewpatterson a écrit :
> Which is the new way?  archetype.xml or archetype-metadata.xml ?
> 
> The "Guide to Creating Archetypes"
> http://maven.apache.org/guides/mini/guide-creating-archetypes.html
> 
> says to use:
> "an archetype descriptor (archetype.xml in directory:
> src/main/resources/META-INF/maven/)."
> 
> but then it also says:
> "Note: this mini-guide has been written for archetype plugin version 1.0.x.
> Archetype plugin 2.0.x is a new generation that fully supports archetypes
> created for 1.0.x, and adds a _new_archetype_descriptor_: it's more
> fexible, has more features, but the basis si absolutely the same."
> 
> The "_new_archetype_descriptor_ link" takes me to
> http://maven.apache.org/archetype/archetype-common/archetype.html
> which says: "Maven's model for the old archetype descriptor (ie for
> Archetype 1.0.x). "
> 
> 
> I hope the new one is archetype-metadata.xml, which is documented here:
> http://maven.apache.org/archetype/maven-archetype-plugin/specification/arch
> etype-metadata.html (which has the awkward title "How metadata on an
> archetype is stored?", yes it does have a question mark)
> 
> The archetype-metadata.xml has the "packaged" option, which I'd like to use
> in my archetype.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multiple profile execution in maven

[Jesse Farinacci]

Greetings,

On Thu, Aug 26, 2010 at 11:29 PM, Sridhar Laxmipuram Srinivasan
 wrote:
> I have tried everything ie with multiple -Ps, comma separated list but in 
> vain :), I think it is a bug, if anybody has any workaround please let me know
>

$ echo "This worked for me just 2 minutes ago!"
$ mvn -P mysql,deployment package jetty:run-war

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Multiple profile execution in maven

[Sridhar Laxmipuram Srinivasan]

I have tried everything ie with multiple -Ps, comma separated list but in vain 
:), I think it is a bug, if anybody has any workaround please let me know

Thnkx
sridharl

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: Thursday, August 26, 2010 6:40 PM
To: Maven Users List
Subject: Re: Multiple profile execution in maven

I checked the docs at maven.apache.org and they say comma list. But as
always, there might be bugs...:-)

/Anders

On Thu, Aug 26, 2010 at 14:42, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I think you use multiple -P's to activate them
>
> -Px -Py
>
> but that could all just be my imagination ;-)
>
> On 26 August 2010 12:33, Anders Hammar  wrote:
>
> > It should work. However, I'm not sure if I have ever enabled more than
> one
> > profile from command line.
> > Just for the heck of it, could you try adding a space between -P and the
> > profiles list ("-P x,y")?
> >
> > /Anders
> >
> > On Thu, Aug 26, 2010 at 13:16, Sridhar Laxmipuram Srinivasan <
> > sridh...@yahoo-inc.com> wrote:
> >
> > > Hi,
> > > I have 2 profiles which are deactivated by default but at run time I
> need
> > > to execute both of them, I have tried with -P, but of no use it
> > always
> > > executes the latter, Could you kindly provide me a solution to this. I
> am
> > > using maven 2.2.1 version
> > >
> > > thnkx
> > > sridharl
> > >
> > >
> >
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

question on capabilities of AntRun plugin

[Jacob Beard]

Hi,

I have question on the capabilities of the AntRun plugin. This example 
shows the Maven classpaths being copied into Ant properties, which are 
then used in Ant:


http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html

I thougth it would be useful to reference these classpaths directly in 
Ant, rather than using the copied properties, and so I ran a series of 
tests. What I found was that the maven classpaths could be referenced, 
but only in the scope of the called target. When used outside of a 
target (in a taskdef, for example), an error is thrown. On the other 
hand, properties that are created in the Maven tasks element can be used 
both in and outside of the scope of the called target. This is using the 
ant task, with both inheritsAll and inheritsRefs set to true.


I'm wondering if I'm correct in the above assessment of the capabilities 
of antrun. Can maven classpaths not be referenced directly, outside of 
the scope of the called ant task? If they cannot, what is the best way 
in Ant to read a classpath that has been read into a property back into 
a path element?


Let me know. Thanks,

Jake

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Is the archetype creation documentation confusing to anyone else?

[lukewpatterson]

Which is the new way?  archetype.xml or archetype-metadata.xml ?

The "Guide to Creating Archetypes"
http://maven.apache.org/guides/mini/guide-creating-archetypes.html

says to use:
"an archetype descriptor (archetype.xml in directory:
src/main/resources/META-INF/maven/)."

but then it also says:
"Note: this mini-guide has been written for archetype plugin version 1.0.x.
Archetype plugin 2.0.x is a new generation that fully supports archetypes
created for 1.0.x, and adds a _new_archetype_descriptor_: it's more fexible,
has more features, but the basis si absolutely the same."

The "_new_archetype_descriptor_ link" takes me to
http://maven.apache.org/archetype/archetype-common/archetype.html
which says: "Maven's model for the old archetype descriptor (ie for
Archetype 1.0.x). "


I hope the new one is archetype-metadata.xml, which is documented here:
http://maven.apache.org/archetype/maven-archetype-plugin/specification/archetype-metadata.html
(which has the awkward title "How metadata on an archetype is stored?", yes
it does have a question mark)

The archetype-metadata.xml has the "packaged" option, which I'd like to use
in my archetype.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Is-the-archetype-creation-documentation-confusing-to-anyone-else-tp2739300p2739300.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to deploy secondary artifacts using deploy plugin

[Victor Calvello]

Thanks Kalle, worked like a charm!

On Thu, Aug 26, 2010 at 5:20 PM, Kalle Korhonen
wrote:

> You need to tell Maven about the additional artifacts. Attach them to
> your module with buildhelper plugin, specifying a different
> type/classifier. See
> http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
>
> Kalle
>
>
> On Thu, Aug 26, 2010 at 1:02 PM, Victor Calvello 
> wrote:
> > Hi guys,
> >
> > I'm trying to deploy to a release nexus repository 2 artifacts with the
> same
> > GAV but different classifier and packaging using the maven-deploy-plugin.
> > The first one goes well. The problem is that fails when wants to upload
> or
> > generate the pom for the second artifact because the first artifact
> uploaded
> > already created it.
> >
> > Is there a way to add secondary artifacts using this plugin?
> >
> > Thanks,
> > Vic
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Change development version

[C. Benson Manica]

Maybe indeed!  This solves a lot of problems - thanks!

On Thu, Aug 26, 2010 at 11:27 AM, Schrecker, Wolfgang <
wolfgang.schrec...@atosorigin.com> wrote:

> Maybe this plugin would help:
> http://mojo.codehaus.org/versions-maven-plugin/
>
> W.
>
> -Ursprüngliche Nachricht-
> Von: C. Benson Manica [mailto:cbman...@gmail.com]
> Gesendet: Donnerstag, 26. August 2010 17:23
> An: Maven Users List
> Betreff: Change development version
>
> What is the "proper" way to update the development version of a project
> (and
> its subprojects if any)?  Say a project is currently at 1.4-SNAPSHOT but I
> decide I want to mark it as 1.4-pre-1-SNAPSHOT - is there a way to do that
> without manually editing all the poms involved?
>
> --
> C. Benson Manica
> cbman...@gmail.com
>
>
>
> --
>
> Atos Worldline Processing GmbH
> Hahnstraße 25
> 60528 Frankfurt/Main
> Germany
> Phone: +49 69/6657-1176
> Fax:
> Mobile:
> mailto: wolfgang.schrec...@atosorigin.com
> http://www.atosworldline.com
>
> Geschäftsführer: Wolf Kunisch
> Aufsichtsratsvorsitzender: Didier Dhennin
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
> * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
> This e-mail and the documents attached are confidential and intended solely
> for the addressee; it may also be privileged. If you receive this e-mail by
> error, please notify the sender immediately and destroy it. As its integrity
> cannot be secured on the internet, the Atos Origin group liability cannot be
> triggered for the message content. Although the sender endeavours to
> maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and shall not be liable for any damages
> resulting from any virus transmitted.
> * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
C. Benson Manica
cbman...@gmail.com

Re: nexus, local repository, and m2eclipse

[Anders Hammar]

A Bot? Are we talking about Martin? :-)

/Anders

On Thu, Aug 26, 2010 at 16:58, Wayne Fay  wrote:

> >  Maybe a good idea is to put a pointer to the nexus list in the most
> obvious
> > place(s) people would look in the Maven on-line docs, saying something
> like "for
> > questions about Nexus, please post to the Nexus mailing list(s) found
> here".
>
> But Nexus is not the only MRM around, so should the Maven docs include
> links to all MRM tools each time the subject comes up? Eventually you
> have to expect that intelligent people can figure out what tool is the
> cause of a given issue and send email to the proper place, right?
>
> I think the problem is simply that it is hard for relatively new
> people to figure out where the "lines" are drawn, which is what Chad
> said. For those of us who have been using these tools for a while, it
> is pretty obvious.
>
> Perhaps we could adjust the mailing software that runs this list so
> emails go through a bot before being distributed. If the word Nexus
> (and other words) is mentioned more than once or if its in the
> subject, then the bot replies back with "are you sure you didn't mean
> to send this to the Nexus list?" and requires a confirmation before
> forwarding it on to the Maven Users group. ;-)
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: No inherited profiles in effective-pom

[Anders Hammar]

But the config of profile in the parent is applied to the pom, right? I
believe that's how it should be.

/Anders
On Thu, Aug 26, 2010 at 16:41, Hoehmann, Andreas <
andreas.hoehmann@siemens.com> wrote:

> Hello,
>
> I have parent artifact with a child artifact.
> The parent contains a profile "foo".
> The child contains a profile "bar".
>
> "mvn help:effective-pom" in child doesn't show the foo profile from parent
> but shows the "bar" profile.
>
> Is this a feature or a bug? ;)
>
> Regards
> Andreas
> -[http://www.ahoehma.de]-
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: How to deploy secondary artifacts using deploy plugin

[Kalle Korhonen]

You need to tell Maven about the additional artifacts. Attach them to
your module with buildhelper plugin, specifying a different
type/classifier. See
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html

Kalle


On Thu, Aug 26, 2010 at 1:02 PM, Victor Calvello  wrote:
> Hi guys,
>
> I'm trying to deploy to a release nexus repository 2 artifacts with the same
> GAV but different classifier and packaging using the maven-deploy-plugin.
> The first one goes well. The problem is that fails when wants to upload or
> generate the pom for the second artifact because the first artifact uploaded
> already created it.
>
> Is there a way to add secondary artifacts using this plugin?
>
> Thanks,
> Vic
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

How to deploy secondary artifacts using deploy plugin

[Victor Calvello]

Hi guys,

I'm trying to deploy to a release nexus repository 2 artifacts with the same
GAV but different classifier and packaging using the maven-deploy-plugin.
The first one goes well. The problem is that fails when wants to upload or
generate the pom for the second artifact because the first artifact uploaded
already created it.

Is there a way to add secondary artifacts using this plugin?

Thanks,
Vic

Re: Question to: "No primary artifact to install..."

[Anders Hammar]

Nope, it's in the super-POM. I might remember the name incorrectly, but it
exists. You can trigger it by a property as well (I think it
performRelease=true).
It should work for snapshots as well. However, I've never tried it. It
attaches sources and javadocs.

One note though: I've seen comments from the devs that this profile
will/might be removed in the future. But it still exists in Maven 3.0-betas.

/Anders

On Thu, Aug 26, 2010 at 16:19, Vincent Latombe wrote:

> Huh? Is this some kind of predefined profile? I think you got mixed up
> Anders ;)
>
>
> 2010/8/26 Anders Hammar 
>
> > mvn install -P release-profile
> >
> > Should do it.
> >
> > /Anders (mobile)
> >
> > Den 2010 8 26 16:13 skrev "Thomas Trepper"  >:
> > > Hi Mathus,
> > >
> > > thanks a lot for your help. I have updated my pom as you told me and I
> > > executed mvn install, which works. Thanks a lot. But it produces only
> > > the main jar. But I want to have javadoc, sources, etc also as jars,
> > > therefore I executed
> > > mvn clean source:jar source:test-jar jar:test-jar javadoc:jar install
> > > which now works also fine, it produces all jars as wanted, BUT source,
> > > doc, test and test-source are ALSO included in the main-jar, which is
> > > *not*, what I want.
> > >
> > > How can I produce main artifact-jar and additionally (NOT included)
> > > javadoc, sources, test and test-sources-jars?
> > >
> > > Thanks everybody till now,
> > >
> > > Thomas
> > >
> > >
> > >
> > >
> > > Am 26.08.2010 16:03, schrieb Baptiste MATHUS:
> > >> First, I've simplified the pom your provided.
> > >> http://pastebin.com/64XC39VS is totally equivalent for what you put.
> > >>
> > >> Could you run mvn install and show us the output?
> > >>
> > >> Thanks
> > >>
> > >> 2010/8/26 Baptiste MATHUS
> > >>
> > >>> Specifying that many plugins as you did is just a mean of getting in
> > >>> trouble soon.
> > >>> Launching a specific plugin, particularly some, with maven is
> something
> > one
> > >>> almost never does.
> > >>>
> > >>> You'd better post here what's the problem running mvn package. This
> > should
> > >>> work this way, simply.
> > >>>
> > >>> Using maven the way you show is ant'ish, and it's not getting to the
> > point
> > >>> where a classical mvn package just package the project, even when not
> > >>> knowing anything about your project.
> > >>>
> > >>> Cheers
> > >>>
> > >>> 2010/8/26 Thomas Trepper
> > >>>
> > >>> Yes, I tried that first, but it did not work and during the
> experiments
> > to
> >  solve the issue the long commandline arised. Sorry for that, but the
> > simple
> >  mvn install did not do it either. I will get the same error...
> > 
> > 
> >  Am 26.08.2010 15:12, schrieb Anders Hammar:
> > 
> >  Why the extremely troublesome mvn command line? Why not just "mvn
> > > install"?
> > >
> > > /Anders
> > >
> > > On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
> > > wrote:
> > >
> > > Hi all,
> > >> this is a snippet from my build, which says, that I have an
> artifact
> > and
> > >> attached artifacts, but, whatever I am doing, I always get the
> > message:
> > >> No
> > >> primary artifact to install, installing attached artifacts
> instead.
> > >>
> > >> Can anybody point me to the right direction please?
> > >>
> > >> Thanks a lot and best regards,
> > >>
> > >> Thomas
> > >>
> > >> P.S: I start my build from eclipse with the following targets:
> > >> clean validate initialize resources:resources compiler:compile
> > >> jar:jar
> > >> source:jar source:test-jar jar:test-jar javadoc:jar test
> > install:install
> > >>
> > >>
> > >>
> > >> [INFO]
> > >> [INFO] --- maven-install-plugin:2.3:install (default-cli) @
> > logging-api
> > >> ---
> > >> [DEBUG] Created new class realm
> > >> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> > >> [DEBUG] Populating class realm
> > >> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> > >> [DEBUG] Included:
> > >> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
> > >> [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
> > >> [DEBUG] Included: junit:junit:jar:3.8.1
> > >> [DEBUG] Included: org.codehaus.plexus:plexus-digest:jar:1.0
> > >> [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
> > >> [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6
> > >> [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.6
> > >> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.6
> > >> [DEBUG] Excluded:
> > >>
> > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
> > >> [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2
> > >> [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.6
> > >> [DEBUG] Excluded:
> org.apache.maven:maven-artifact-manager:jar:2.0.6
> > >> [DEBUG] Excluded:
> > org

Re: Why all these errors with mvn site:site concerning https://maven-repository.dev.java.net/nonav/repository

[Fabricio Lemos]

 I´m also getting this error with maven 3.0-beta-2 and site plugin 
3.0-beta-1.


Can you point me to the Jira issue for this bug?

thanks,
Fabricio Lemos

On 29/7/2010 02:19, Rick R wrote:

On Tue, Jul 27, 2010 at 4:34 PM, Brian Fox  wrote:


one of the reports in there hits all repos known to the build. There's
a bug against it.


Is there a known work around in the meantime?



On Tue, Jul 27, 2010 at 2:29 PM, Rick R  wrote:

I keep getting all these errors about
https://maven-repository.dev.java.net/nonav/repository. I tried googling
about it but the responses are confusing.
(I'm using maven 2.2.1 and 2.1.1 of the site plugin)

 tons more.
[ERROR] Unable to determine if resource
org.springframework:spring-context-support:jar:2.5.5:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource
org.springframework:spring-core:jar:2.5.5:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource
org.springframework:spring-jms:jar:2.5.5:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource
org.springframework:spring-tx:jar:2.5.5:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource
org.springframework:spring-web:jar:2.5.5:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource oro:oro:jar:2.0.8:compile exists

in

https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource rhino:js:jar:1.7R1:compile exists

in

https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource

taglibs:standard:jar:1.1.2:compile

exists in https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource tomcat:jsp-api:jar:5.5.23:test
exists in https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource wsdl4j:wsdl4j:jar:1.6.2:compile
exists in https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource xom:xom:jar:1.0:compile exists in
https://maven-repository.dev.java.net/nonav/repository
[ERROR] Unable to determine if resource xpp3:xpp3_min:jar:1.1.4c:compile
exists in https://maven-repository.dev.java.net/nonav/repository


--
Rick R


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Ear plugin issue

[EJ Ciramella]

With -X -e, is it any clearer as to what it's looking for?  What the GAV is?



-Original Message-
From: nishant@hsbcib.com [mailto:nishant@hsbcib.com]
Sent: Thursday, August 26, 2010 1:37 PM
To: Maven Users List
Cc: Maven Users List
Subject: Re: Ear plugin issue

Just that unable to find clientModule






Stephane Nicoll 
Aug 26 2010 18:35

Mail Size: 10664

Please respond to
"Maven Users List" 


To
Maven Users List 
cc

Subject
Re: Ear plugin issue

  Entity
   HSBC Bank plc - HBEU



What error message do you get exactly? ClientModules is not a dependency
of
the project or something else?

S.

On Thu, Aug 26, 2010 at 4:20 PM,  wrote:

> It seems the attachments are not allowed. I have included the ear pom
> below..
>
>
>
**
> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>  4.0.0
>  
>ProjectX
>root
>1.0
>  
>  root.ProjectX
>  EarAssembler
>  1.0
>  EarAssembler
>  ear
>  
>
>  
>org.apache.maven.plugins
>maven-ear-plugin
>2.4.2
>
>  
>
>  root.ProjectX
>  ClientModules
>
>  
>  
>
>  true
>
>  
>
>  
>
>  
>  
>
>  root.ProjectX
>  ClientModules
>  1.0
>
>  
> 
>
>
**
>
>
> Thanks
>
>
>
>
> Nishant RAJ/HBEU/h...@hsbc
> Aug 26 2010 15:17
>
> Mail Size: 8020
>
> Please respond to
> "Maven Users List" 
>
>
> To
> users@maven.apache.org
> cc
>
> Subject
> Ear plugin issue
>
>  Entity
>   HSBC Bank plc - HBEU
>
>
>
>
> Hi All,
>
> I am trying to get the ear plugin working.
>
> Followed all the guidelines but could not get it working as its not able
> to "find" the module that I want to package within the ear
>
> It looks for the module in my nexus repository but does not find it.
> I have also got the "Resolve workspace project dependencies" enables in
> eclipse.
>
> Pom is attached.
>
> Please advice as I have been struggling with the same for few hrs now.
>
> Thanks
> Nishant
>
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
> - SAVE PAPER - THINK BEFORE YOU
> PRINT! This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page attached
> hereto must be read in conjunction with any disclaimer which forms part
of
> it. Unless otherwise stated, this transmission is neither an offer nor
the
> solicitation of an offer to sell or purchase any investment. Its
contents
> are based on information obtained from sources believed to be reliable
but
> HSBC makes no representation and accepts no responsibility or liability
as
> to its completeness or accuracy.
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
>
>
> -
> SAVE PAPER - THINK BEFORE YOU PRINT!
>
> This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page
> attached hereto must be read in conjunction with any disclaimer
> which forms part of it. Unless otherwise stated, this transmission
> is neither an offer nor the solicitation of an offer to sell or
> purchase any investment. Its contents are based on information
> obtained from sources believed to be reliable but HSBC makes no
> representation and accepts no responsibility or liability as to its
> completeness or accuracy.
>



*

Re: Ear plugin issue

[nishant . raj]

Just that unable to find clientModule






Stephane Nicoll  
Aug 26 2010 18:35

Mail Size: 10664

Please respond to
"Maven Users List" 


To
Maven Users List 
cc

Subject
Re: Ear plugin issue

  Entity
   HSBC Bank plc - HBEU



What error message do you get exactly? ClientModules is not a dependency 
of
the project or something else?

S.

On Thu, Aug 26, 2010 at 4:20 PM,  wrote:

> It seems the attachments are not allowed. I have included the ear pom
> below..
>
>
> 
**
> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>  4.0.0
>  
>ProjectX
>root
>1.0
>  
>  root.ProjectX
>  EarAssembler
>  1.0
>  EarAssembler
>  ear
>  
>
>  
>org.apache.maven.plugins
>maven-ear-plugin
>2.4.2
>
>  
>
>  root.ProjectX
>  ClientModules
>
>  
>  
>
>  true
>
>  
>
>  
>
>  
>  
>
>  root.ProjectX
>  ClientModules
>  1.0
>
>  
> 
>
> 
**
>
>
> Thanks
>
>
>
>
> Nishant RAJ/HBEU/h...@hsbc
> Aug 26 2010 15:17
>
> Mail Size: 8020
>
> Please respond to
> "Maven Users List" 
>
>
> To
> users@maven.apache.org
> cc
>
> Subject
> Ear plugin issue
>
>  Entity
>   HSBC Bank plc - HBEU
>
>
>
>
> Hi All,
>
> I am trying to get the ear plugin working.
>
> Followed all the guidelines but could not get it working as its not able
> to "find" the module that I want to package within the ear
>
> It looks for the module in my nexus repository but does not find it.
> I have also got the "Resolve workspace project dependencies" enables in
> eclipse.
>
> Pom is attached.
>
> Please advice as I have been struggling with the same for few hrs now.
>
> Thanks
> Nishant
>
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
> - SAVE PAPER - THINK BEFORE YOU
> PRINT! This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page attached
> hereto must be read in conjunction with any disclaimer which forms part 
of
> it. Unless otherwise stated, this transmission is neither an offer nor 
the
> solicitation of an offer to sell or purchase any investment. Its 
contents
> are based on information obtained from sources believed to be reliable 
but
> HSBC makes no representation and accepts no responsibility or liability 
as
> to its completeness or accuracy.
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
>
>
> -
> SAVE PAPER - THINK BEFORE YOU PRINT!
>
> This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page
> attached hereto must be read in conjunction with any disclaimer
> which forms part of it. Unless otherwise stated, this transmission
> is neither an offer nor the solicitation of an offer to sell or
> purchase any investment. Its contents are based on information
> obtained from sources believed to be reliable but HSBC makes no
> representation and accepts no responsibility or liability as to its
> completeness or accuracy.
>




HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



--

Re: Ear plugin issue

[Stephane Nicoll]

What error message do you get exactly? ClientModules is not a dependency of
the project or something else?

S.

On Thu, Aug 26, 2010 at 4:20 PM,  wrote:

> It seems the attachments are not allowed. I have included the ear pom
> below..
>
>
> **
> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>  4.0.0
>  
>ProjectX
>root
>1.0
>  
>  root.ProjectX
>  EarAssembler
>  1.0
>  EarAssembler
>  ear
>  
>
>  
>org.apache.maven.plugins
>maven-ear-plugin
>2.4.2
>
>  
>
>  root.ProjectX
>  ClientModules
>
>  
>  
>
>  true
>
>  
>
>  
>
>  
>  
>
>  root.ProjectX
>  ClientModules
>  1.0
>
>  
> 
>
> **
>
>
> Thanks
>
>
>
>
> Nishant RAJ/HBEU/h...@hsbc
> Aug 26 2010 15:17
>
> Mail Size: 8020
>
> Please respond to
> "Maven Users List" 
>
>
> To
> users@maven.apache.org
> cc
>
> Subject
> Ear plugin issue
>
>  Entity
>   HSBC Bank plc - HBEU
>
>
>
>
> Hi All,
>
> I am trying to get the ear plugin working.
>
> Followed all the guidelines but could not get it working as its not able
> to "find" the module that I want to package within the ear
>
> It looks for the module in my nexus repository but does not find it.
> I have also got the "Resolve workspace project dependencies" enables in
> eclipse.
>
> Pom is attached.
>
> Please advice as I have been struggling with the same for few hrs now.
>
> Thanks
> Nishant
>
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
> - SAVE PAPER - THINK BEFORE YOU
> PRINT! This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page attached
> hereto must be read in conjunction with any disclaimer which forms part of
> it. Unless otherwise stated, this transmission is neither an offer nor the
> solicitation of an offer to sell or purchase any investment. Its contents
> are based on information obtained from sources believed to be reliable but
> HSBC makes no representation and accepts no responsibility or liability as
> to its completeness or accuracy.
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
>
>
> -
> SAVE PAPER - THINK BEFORE YOU PRINT!
>
> This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page
> attached hereto must be read in conjunction with any disclaimer
> which forms part of it. Unless otherwise stated, this transmission
> is neither an offer nor the solicitation of an offer to sell or
> purchase any investment. Its contents are based on information
> obtained from sources believed to be reliable but HSBC makes no
> representation and accepts no responsibility or liability as to its
> completeness or accuracy.
>

Re: Correcting a groupID

[Vincent Latombe]

You'll need a dependencyManagement to force A to use c-n:c-n:12 which will
depends on org.apache.commons.net:c-n:12.

2010/8/26 Benson Margulies 

> On Thu, Aug 26, 2010 at 8:41 AM, Stephen Connolly
>  wrote:
> > Why not have commons-net:commons-net become an empty jar which has a
> > dependency on org.apache.commons:net
> >
> > that way, anyone with the old GA coords will just have an empty jar on
> their
> > classpath and the correct jar as well
>
> i don't see it.
>
> Component A is sitting out there with a dependency on c-n:c-n:1
>
> Component B has a dependency on A and also on c-n:c-n:1
>
> Sebb changes the group ID.
>
> Now, A still depends on c-n:c-n:1
> B depends on org.apache.commons.net:c-n:12, and on A
> And we've got two dueling versions in classpath.
>
> It doesn't help to release a new version c-n:c-n:12, since A isn't
> using a range, it's pointing at '1'.
>
> Am I missing something?
>
>
>
>
>
>
> >
> > On 26 August 2010 00:13, Benson Margulies  wrote:
> >
> >> Let me recap the pain scenario here:
> >>
> >> Existing poms reference commons-net under the old group ID.
> >>
> >> commons-net releases a new version under a new group ID.
> >>
> >> Dependencies under the old group ID won't be seen as 'the same thing'
> >> as the new group ID, so
> >>
> >> a project that references the new group ID and has a dependency that
> >> uses the old group ID gets both in the classpath, and probably
> >> experiences chaos until repaired with exclusions.
> >>
> >> Unless maven grew a feature whereby the new artifact could explicitly
> >> declare itself a successor of the old one under the other name, this
> >> is unavoidable. Either don't rename or live with this as an annoyance
> >> to the users of the new version. Renaming packages might help, insofar
> >> as the two versions might then coexist happily.
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Vincent

Re: Maven community maintaining popular JS lib deps? (was: Re: downloading JavaScript libraries)

[Jesse Farinacci]

Greetings,

On Thu, Aug 26, 2010 at 12:53 PM, Manos Batsis
 wrote:
>
> The only reason to package those javascript files in JARs and upload them to
> the maven central repo is for other projects to reuse them as dependencies.
> I don't think this is your case.

This definitely wasn't what he asked to do, and you were right to
answer him directly. I answered the question that I think he *should*
have asked.. ;-) Perhaps complicating things far too much..

> On the other hand and since most javascript projects do not produce maven
> dependencies for the maven users out there, it might make sense to establish
> a community in this list to maintain popular JS lib dependencies.
>
> Some questions to list members:
>
>  - Does it sound like a good idea and why?
>  - How should we go for it in organizing a team of maintainers?
>  - How should those JS libs packaged?

There's already a javascript project on codehaus[1], I am surprised
that they do not already publish Maven artifacts for popular
frameworks. I'd recommend publish them in a variety of formats:

 * maven-remote-resource-bundle
 * jar
 * war

The first could be used to seed the second and third. Let the users
choose for themselves which works best for them..

-Jesse

[1] http://mojo.codehaus.org/javascript-maven-tools/

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Jesse Farinacci]

Hi Jake,

On Thu, Aug 26, 2010 at 11:51 AM, Jacob Beard  wrote:
>
> I think this is where my comprehension is breaking down. In order for other
> users to automatically download these new JavaScript library modules that I
> would create, would these new modules need to be published in a Maven
> repository? Or is there another mechanism involved in distributing these
> libraries?

I think you're getting it now! No worries :-) Ok, yes, you would
create these artifacts yourself and then publish them. You probably
would not have any luck getting them into Maven central so you'd want
a Maven Repository Manager (MRM) available. There are a few which are
freely available, I would recommend Nexus[1] or Archiva[2]; but
there's an alternate means if you do not want to go through the very
limited hassle.

You could also create a file system which is in the right format of a
Maven repository. Then you could just use mvn deploy to push them to
that file system using scp, e.g. Then your web server would sort of
act like an MRM of limited scope. It'd probably be easier to just set
up one of the aforementioned MRMs and be done with it.

> Thanks for your patience in explaining this issue,

You're picking it up quick, so that's always positive!
-Jesse

[1] http://nexus.sonatype.org/download-nexus.html
[2] http://archiva.apache.org/download.html

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven community maintaining popular JS lib deps? (was: Re: downloading JavaScript libraries)

[Manos Batsis]

On 08/26/2010 06:51 PM, Jacob Beard wrote:

On 10-08-26 11:27 AM, Jesse Farinacci wrote:

Making them proper Maven modules and populating them ONE time manually
when you create the artifact would enable all of your users to
automatically download the artifact which contains the javascript
library.


I think this is where my comprehension is breaking down. In order for
other users to automatically download these new JavaScript library
modules that I would create, would these new modules need to be
published in a Maven repository? Or is there another mechanism involved
in distributing these libraries?


The only reason to package those javascript files in JARs and upload 
them to the maven central repo is for other projects to reuse them as 
dependencies. I don't think this is your case.


On the other hand and since most javascript projects do not produce 
maven dependencies for the maven users out there, it might make sense to 
establish a community in this list to maintain popular JS lib dependencies.


Some questions to list members:

 - Does it sound like a good idea and why?
 - How should we go for it in organizing a team of maintainers?
 - How should those JS libs packaged?

Especially for the latter, i think some people use WAR overlays, others 
like me use JARs and resource loading and there may even be other ways. 
The packaging should be usable for both common and web applications.


Another thing is a)versioning and b)alternatives for the same file. What 
we do here at abiss is:


 - Versioning: the browser always makes a request for (e.g.) 
"/resources/gr/abiss/js/sarissa.js" and our maven-jstools-plugin [1] 
servlet filter [2]loads the script version that was included as a POM 
dependency.
 - Alternative versions of the same file like compressed/minified are 
loaded based on convension e.g. sarissa.js sarissa-min.js


Other of course may have better ideas for the table, but overall it may 
be a good time to establish at least a community of dep maintainers for 
popular JS libs.


[1] http://dev.abiss.gr/mvn-jstools/
[2] 
http://dev.abiss.gr/mvn-jstools/apidocs/gr/abiss/mvn/plugins/jstools/web/JavascriptDependencyFilter.html


Cheers,

Manos


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Jacob Beard]

Hi Jesse,

On 10-08-26 11:27 AM, Jesse Farinacci wrote:

Making them proper Maven modules and populating them ONE time manually
when you create the artifact would enable all of your users to
automatically download the artifact which contains the javascript
library.


I think this is where my comprehension is breaking down. In order for 
other users to automatically download these new JavaScript library 
modules that I would create, would these new modules need to be 
published in a Maven repository? Or is there another mechanism involved 
in distributing these libraries?


Thanks for your patience in explaining this issue,

Jake

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Correcting a groupID

[Benson Margulies]

On Thu, Aug 26, 2010 at 8:41 AM, Stephen Connolly
 wrote:
> Why not have commons-net:commons-net become an empty jar which has a
> dependency on org.apache.commons:net
>
> that way, anyone with the old GA coords will just have an empty jar on their
> classpath and the correct jar as well

i don't see it.

Component A is sitting out there with a dependency on c-n:c-n:1

Component B has a dependency on A and also on c-n:c-n:1

Sebb changes the group ID.

Now, A still depends on c-n:c-n:1
B depends on org.apache.commons.net:c-n:12, and on A
And we've got two dueling versions in classpath.

It doesn't help to release a new version c-n:c-n:12, since A isn't
using a range, it's pointing at '1'.

Am I missing something?






>
> On 26 August 2010 00:13, Benson Margulies  wrote:
>
>> Let me recap the pain scenario here:
>>
>> Existing poms reference commons-net under the old group ID.
>>
>> commons-net releases a new version under a new group ID.
>>
>> Dependencies under the old group ID won't be seen as 'the same thing'
>> as the new group ID, so
>>
>> a project that references the new group ID and has a dependency that
>> uses the old group ID gets both in the classpath, and probably
>> experiences chaos until repaired with exclusions.
>>
>> Unless maven grew a feature whereby the new artifact could explicitly
>> declare itself a successor of the old one under the other name, this
>> is unavoidable. Either don't rename or live with this as an annoyance
>> to the users of the new version. Renaming packages might help, insofar
>> as the two versions might then coexist happily.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Jesse Farinacci]

Greetings,

On Thu, Aug 26, 2010 at 10:54 AM, Jacob Beard  wrote:
>
> I'm new to Maven, and so I don't completely understand your answer. Why
> would it be desirable to create a module for each JavaScript library in this
> context, especially as this will not facilitate their automated downloading?

It would be desirable because your project has a dependency which is
not part of the Maven ecosystem. Your project managing the download of
dependencies is the antithesis of one of Maven's best features

Making them proper Maven modules and populating them ONE time manually
when you create the artifact would enable all of your users to
automatically download the artifact which contains the javascript
library.

> Also, it still seems like it would be desirable to instruct maven to
> automatically download these libraries, so that they will not need to be
> downloaded manually. Is there no way to instruct Maven to do this?

Maven doesn't do well, nor was it designed to do well, with managing
non-Maven artifacts. And this is what you're asking it to do. I also
think you seem to be confusing Maven downloading a Maven artifact
dependency and you downloading some javascript library which is not a
Maven module. I suggest you do the latter one single time, manually,
and create a proper Maven module. I also suggest you do the former
automatically with Maven and standard Maven dependency resolution once
the previous step is complete.

If you want to continue to do things against The Maven Way, then you
should fall back to the maven-antrun-plugin method which has already
been described. I think this would be quite an error, but, alas,
you're free to do whatever you want..

> Please let me know what you think. Thanks,

Perhaps someone else can step in and explain, I don't think I be
clearer than I have been..

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: Change development version

[Schrecker, Wolfgang]

Maybe this plugin would help:
http://mojo.codehaus.org/versions-maven-plugin/

W.

-Ursprüngliche Nachricht-
Von: C. Benson Manica [mailto:cbman...@gmail.com] 
Gesendet: Donnerstag, 26. August 2010 17:23
An: Maven Users List
Betreff: Change development version

What is the "proper" way to update the development version of a project (and
its subprojects if any)?  Say a project is currently at 1.4-SNAPSHOT but I
decide I want to mark it as 1.4-pre-1-SNAPSHOT - is there a way to do that
without manually editing all the poms involved?

-- 
C. Benson Manica
cbman...@gmail.com


 
--

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax: 
Mobile: 
mailto: wolfgang.schrec...@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Wolf Kunisch
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417

* * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail by error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and shall not be liable for any damages resulting from any virus 
transmitted.
* * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Change development version

[C. Benson Manica]

What is the "proper" way to update the development version of a project (and
its subprojects if any)?  Say a project is currently at 1.4-SNAPSHOT but I
decide I want to mark it as 1.4-pre-1-SNAPSHOT - is there a way to do that
without manually editing all the poms involved?

-- 
C. Benson Manica
cbman...@gmail.com

Re: Maven build for compiling JavaScript project

[Jacob Beard]

Hi Manos,

Reply below:

On 10-08-26 11:01 AM, Manos Batsis wrote:
 - Introduce new ant targets without the dependencies to call in each 
appropriate Maven phase, thus preserving the old targets and the Ant 
build behavior to be used if needed and when not working with Maven
This one sounds like a winner. With a little bit of work introducing 
Maven-specific tasks, it should be possible to make the script callable 
directly with Ant, or from Maven.


Jake

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: nexus, local repository, and m2eclipse

[Wayne Fay]

>  Maybe a good idea is to put a pointer to the nexus list in the most obvious
> place(s) people would look in the Maven on-line docs, saying something like 
> "for
> questions about Nexus, please post to the Nexus mailing list(s) found here".

But Nexus is not the only MRM around, so should the Maven docs include
links to all MRM tools each time the subject comes up? Eventually you
have to expect that intelligent people can figure out what tool is the
cause of a given issue and send email to the proper place, right?

I think the problem is simply that it is hard for relatively new
people to figure out where the "lines" are drawn, which is what Chad
said. For those of us who have been using these tools for a while, it
is pretty obvious.

Perhaps we could adjust the mailing software that runs this list so
emails go through a bot before being distributed. If the word Nexus
(and other words) is mentioned more than once or if its in the
subject, then the bot replies back with "are you sure you didn't mean
to send this to the Nexus list?" and requires a confirmation before
forwarding it on to the Maven Users group. ;-)

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Executing ant, but only once

[Baptiste MATHUS]

You're using ant to replace variables or so? This is a standard maven
feature: you want to have a look here
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html


Cheers

2010/8/26 Thomas Trepper 

>  Hi all,
>
> I have now the following part in the pom:
>
> 
> org.apache.maven.plugins
> maven-antrun-plugin
> 
> 
> generate-version-info
> 
> run
> 
> process-sources
> 
> 
> 
> 
> 
> 
> 
> 
>
>
> which should execute an ant-task, which modifies and replaces some entries
> in the sources.  I want this be executed only ONCE and before any artifacts
> are build?
>
> Can anybody point me into the right direction please?
>
> Thanks a lot and best regards,
>
> Thomas
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: downloading JavaScript libraries

[Jacob Beard]

Manos,

Thanks for the reply. This makes good sense to me.

Jake

On 10-08-26 10:54 AM, Manos Batsis wrote:

On 08/26/2010 05:44 AM, Jacob Beard wrote:

My project includes dependencies on several JavaScript libraries,
including Dojo, RequireJS and beautify-js. I'm currently using Ant's get
task to download these dependencies, but I'd like to integrate this with
my Maven build. The way I thought I would do this would be to bind an
antrun goal to the phase in which dependencies are downloaded. However,
after consulting the lifecycle reference
, 


I cannot find a Maven phase in which dependencies are downloaded.


If those are dependencies native to Maven they will be downloaded 
automatically from the central repository or a repository you specify.


If however by "dependencies" you just mean your project depends on 
them and they are not available in the maven repo (you can check for 
example using [1]) then using antrun will be fine. If you just need to 
package them along with everything else choose any phase before 
"p[ackage" (e.g. "prepare-package"). If you want to do more stuff with 
them (i remember you do some JS pre-compile to jave stuff?) then fetch 
them during "generate-sources" or something.


hth,

Manos

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Jacob Beard]

Hi Jesse,

I'm new to Maven, and so I don't completely understand your answer. Why 
would it be desirable to create a module for each JavaScript library in 
this context, especially as this will not facilitate their automated 
downloading?


Also, it still seems like it would be desirable to instruct maven to 
automatically download these libraries, so that they will not need to be 
downloaded manually. Is there no way to instruct Maven to do this?


Please let me know what you think. Thanks,

Jake

On 10-08-25 10:53 PM, Jesse Farinacci wrote:

I don't think you're on the right track, frankly. It would be better
for you to create a module for each of your javascript library
dependencies, and simply manually download it and put it into
src/main/script (or perhaps src/main/resources to allow the easiest
packaging). Set the version number to be whatever version of the
library you're packaging.

Then, in your projects which utilize this javascript, simply depend on
your module with the appropriate version. This would be more The Maven
Way. Good luck!

-Jesse

   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Manos Batsis]

On 08/26/2010 05:54 PM, Manos Batsis wrote:

On 08/26/2010 05:44 AM, Jacob Beard wrote:

My project includes dependencies on several JavaScript libraries,
including Dojo, RequireJS and beautify-js. I'm currently using Ant's get
task to download these dependencies, but I'd like to integrate this with
my Maven build. The way I thought I would do this would be to bind an
antrun goal to the phase in which dependencies are downloaded. However,
after consulting the lifecycle reference
,

I cannot find a Maven phase in which dependencies are downloaded.


If those are dependencies native to Maven they will be downloaded
automatically from the central repository or a repository you specify.


Forgot to say that, for this to work, you will need to add them as 
dependencies in your POM.




If however by "dependencies" you just mean your project depends on them
and they are not available in the maven repo (you can check for example
using [1]) then using antrun will be fine. If you just need to package
them along with everything else choose any phase before "p[ackage" (e.g.
"prepare-package"). If you want to do more stuff with them (i remember
you do some JS pre-compile to jave stuff?) then fetch them during
"generate-sources" or something.

hth,

Manos

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven build for compiling JavaScript project

[Manos Batsis]

On 08/25/2010 11:43 PM, Jacob Beard wrote:

On 10-08-25 02:41 PM, Manos Batsis wrote:

The way I get this, you don't have to change the behavior of Maven's
compiler plugin.

If you check out [1], you'll see there are plenty of lifecycle phases
to hook your ant tasks (or whatnot) and perform steps 1, 2 and 3.

For example, I'd probably use generate-(re)sources/process-(re)sources
to perform 1 and 2.

For step 3, generate-sources is greate for code generation (i.e. if
that jsc thingy produces .java code), otherwise I'd just throw in the
generated class files in the target during prepare-package or,
especially if you need tests, process-classes.



I think you might be right, the way you describe may better integrate
with the Maven lifecycle than having tasks 1,2 and 3 all be executed
within the compile phase. However, it's not clear to me how what you
propose could be implemented using the Maven AntRun plugin. The reason
for this is that, currently in the Ant script, tasks 1, 2, and 3 depend
on one-another such that 3 depends on 2, and 2 depends on 1. This is
desirable, as, when calling the task 3 in the Ant script without Maven,
tasks 1 and 2 should be executed before 3. If one were to delegate to
tasks 1, 2, and 3 at different phases in the Maven lifecycle, then
during the Maven build process, task 1 would be executed, then task 1
followed by task 2, then task 1 followed by 2 followed by 3. It seems
like to change this behaviour would involve removing the dependencies in
the Ant script, which I feel would essentially be "breaking" the script.


You pick any of:

 - Remove the dependencies from the Ant targets and then call each from 
the "appropriate" Maven phase,
 - Introduce new ant targets without the dependencies to call in each 
appropriate Maven phase, thus preserving the old targets and the Ant 
build behavior to be used if needed and when not working with Maven

 - Call 3 from Maven and get done with it.




If I've misunderstood something, or there's a better way to implement
this, please let me know.


Perhaps you would be interested in helping us implement 1-3 in the
maven-jstools-plugin [2] ;-)

Sure. If you don't mind an Ant dependency, then the work is already done:

https://svn.apache.org/repos/asf/commons/sandbox/gsoc/2010/scxml-js/trunk/build.xml


Thanks I'll take a look.



If you have a native Maven plugin in mind, that would be something I
could perhaps assist with in the future as well.


Yes that's what I was thinking, will probably get back to you on that 
after picking at your stuff ;-)


Cheers,

Manos

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

No inherited profiles in effective-pom

[Hoehmann, Andreas]

Hello,

I have parent artifact with a child artifact.
The parent contains a profile "foo". 
The child contains a profile "bar".

"mvn help:effective-pom" in child doesn't show the foo profile from parent but 
shows the "bar" profile.

Is this a feature or a bug? ;)

Regards
Andreas
-[http://www.ahoehma.de]-
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Executing ant, but only once

[Thomas Trepper]

 Hi all,

I have now the following part in the pom:


org.apache.maven.plugins
maven-antrun-plugin


generate-version-info

run

process-sources










which should execute an ant-task, which modifies and replaces some 
entries in the sources.  I want this be executed only ONCE and before 
any artifacts are build?


Can anybody point me into the right direction please?

Thanks a lot and best regards,

Thomas



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: downloading JavaScript libraries

[Manos Batsis]

On 08/26/2010 05:44 AM, Jacob Beard wrote:

My project includes dependencies on several JavaScript libraries,
including Dojo, RequireJS and beautify-js. I'm currently using Ant's get
task to download these dependencies, but I'd like to integrate this with
my Maven build. The way I thought I would do this would be to bind an
antrun goal to the phase in which dependencies are downloaded. However,
after consulting the lifecycle reference
,
I cannot find a Maven phase in which dependencies are downloaded.


If those are dependencies native to Maven they will be downloaded 
automatically from the central repository or a repository you specify.


If however by "dependencies" you just mean your project depends on them 
and they are not available in the maven repo (you can check for example 
using [1]) then using antrun will be fine. If you just need to package 
them along with everything else choose any phase before "p[ackage" (e.g. 
"prepare-package"). If you want to do more stuff with them (i remember 
you do some JS pre-compile to jave stuff?) then fetch them during 
"generate-sources" or something.


hth,

Manos

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Ear plugin issue

[Timothy Mcginnis]

In  add

${project.artifactId}-${project.version}.jar

and make sure your project in Eclipse is named using the 
[artifactId]-[version] Name Template.

Tim McGinnis
717 720-1962
Web Development
AES/PHEAA



From:
nishant@hsbcib.com
To:
"Maven Users List" 
Cc:
users@maven.apache.org
Date:
08/26/2010 10:21 AM
Subject:
Re: Ear plugin issue



It seems the attachments are not allowed. I have included the ear pom 
below..

**
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0
  
ProjectX
root
1.0
  
  root.ProjectX
  EarAssembler
  1.0
  EarAssembler
  ear
  

  
org.apache.maven.plugins
maven-ear-plugin
2.4.2

  

  root.ProjectX
  ClientModules

  
  

  true

  

  

  
  

  root.ProjectX
  ClientModules
  1.0

  

**


Thanks




Nishant RAJ/HBEU/h...@hsbc 
Aug 26 2010 15:17

Mail Size: 8020

Please respond to
"Maven Users List" 


To
users@maven.apache.org
cc

Subject
Ear plugin issue

  Entity
   HSBC Bank plc - HBEU




Hi All, 

I am trying to get the ear plugin working. 

Followed all the guidelines but could not get it working as its not able 
to "find" the module that I want to package within the ear 

It looks for the module in my nexus repository but does not find it. 
I have also got the "Resolve workspace project dependencies" enables in 
eclipse. 

Pom is attached. 

Please advice as I have been struggling with the same for few hrs now. 

Thanks 
Nishant 




HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority

- SAVE PAPER - THINK BEFORE YOU 
PRINT! This transmission has been issued by a member of the HSBC Group 
"HSBC" for the information of the addressee only and should not be 
reproduced and/or distributed to any other person. Each page attached 
hereto must be read in conjunction with any disclaimer which forms part of 

it. Unless otherwise stated, this transmission is neither an offer nor the 

solicitation of an offer to sell or purchase any investment. Its contents 
are based on information obtained from sources believed to be reliable but 

HSBC makes no representation and accepts no responsibility or liability as 

to its completeness or accuracy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



-
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.


==
This message contains privileged and confidential information intended for the 
above addressees only.  If you
receive this message in error please delete or destroy this message and/or 
attachments.  

The sender of this message will fully cooperate in the civil and criminal 
prosecution of any individual engaging
in the unauthorized use of this message.
==

[Solved] Re: Question to: "No primary artifact to install..."

[Thomas Trepper]

 Hi all,

I got the error, it was something inside the old pom, I accidently 
forgot to save before testing.  Sorry for the inconvenience und thank 
you all very much for your help.


Thomas




Am 26.08.2010 16:12, schrieb Thomas Trepper:

 Hi Mathus,

thanks a lot for your help. I have updated my pom as you told me and I 
executed mvn install, which works. Thanks a lot.  But it produces only 
the main jar. But I want to have javadoc, sources, etc also as jars, 
therefore I executed

mvn clean source:jar source:test-jar jar:test-jar javadoc:jar install
which now works also fine, it produces all jars as wanted, BUT source, 
doc, test and test-source are ALSO included in the main-jar, which is 
*not*, what I want.


How can I produce main artifact-jar and additionally (NOT included) 
javadoc, sources, test and test-sources-jars?


Thanks everybody till now,

Thomas




Am 26.08.2010 16:03, schrieb Baptiste MATHUS:

First, I've simplified the pom your provided.
http://pastebin.com/64XC39VS is totally equivalent for what you put.

Could you run mvn install and show us the output?

Thanks

2010/8/26 Baptiste MATHUS


Specifying that many plugins as you did is just a mean of getting in
trouble soon.
Launching a specific plugin, particularly some, with maven is 
something one

almost never does.

You'd better post here what's the problem running mvn package. This 
should

work this way, simply.

Using maven the way you show is ant'ish, and it's not getting to the 
point

where a classical mvn package just package the project, even when not
knowing anything about your project.

Cheers

2010/8/26 Thomas Trepper

  Yes, I tried that first, but it did not work and during the 
experiments to
solve the issue the long commandline arised. Sorry for that, but 
the simple

mvn install did not do it either. I will get the same error...


Am 26.08.2010 15:12, schrieb Anders Hammar:

  Why the extremely troublesome mvn command line? Why not just "mvn

install"?

/Anders

On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
wrote:

   Hi all,
this is a snippet from my build, which says, that I have an 
artifact and
attached artifacts, but, whatever I am doing, I always get the 
message:

No
primary artifact to install, installing attached artifacts instead.

Can anybody point me to the right direction please?

Thanks a lot and best regards,

Thomas

P.S: I start my build from eclipse with the following targets:
clean validate initialize  resources:resources compiler:compile
  jar:jar
source:jar source:test-jar jar:test-jar javadoc:jar test 
install:install




[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-cli) @ 
logging-api

---
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG]   Included:
org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 


[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: 
org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: 
org.apache.maven:maven-repository-metadata:jar:2.0.6

[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-install-plugin:2.3:install' with 
basic

configurator -->
[DEBUG]   (f) artifact = 
com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT

[DEBUG]   (f) attachedArtifacts =
[com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
[DEBUG]   (f) createChecksum = false
[DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

[DEBUG]   (f) packaging = jar
[DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] No primary artifact to install, installing attached artifacts
instead.
[INFO] Installing E:\workspace.utils\logging-api\pom.xml to

C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom 


[INFO] Installing

E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar 


to

C:\eclipse-SDK-3.6\mav

Re: Ear plugin issue

[nishant . raj]

It seems the attachments are not allowed. I have included the ear pom 
below..

**
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0
  
ProjectX
root
1.0
  
  root.ProjectX
  EarAssembler
  1.0
  EarAssembler
  ear
  

  
org.apache.maven.plugins
maven-ear-plugin
2.4.2

  

  root.ProjectX
  ClientModules

  
  

  true

  

  

  
  

  root.ProjectX
  ClientModules
  1.0

  

**


Thanks




Nishant RAJ/HBEU/h...@hsbc 
Aug 26 2010 15:17

Mail Size: 8020

Please respond to
"Maven Users List" 


To
users@maven.apache.org
cc

Subject
Ear plugin issue

  Entity
   HSBC Bank plc - HBEU




Hi All, 

I am trying to get the ear plugin working. 

Followed all the guidelines but could not get it working as its not able 
to "find" the module that I want to package within the ear 

It looks for the module in my nexus repository but does not find it. 
I have also got the "Resolve workspace project dependencies" enables in 
eclipse. 

Pom is attached. 

Please advice as I have been struggling with the same for few hrs now. 

Thanks 
Nishant 




HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority

- SAVE PAPER - THINK BEFORE YOU 
PRINT! This transmission has been issued by a member of the HSBC Group 
"HSBC" for the information of the addressee only and should not be 
reproduced and/or distributed to any other person. Each page attached 
hereto must be read in conjunction with any disclaimer which forms part of 
it. Unless otherwise stated, this transmission is neither an offer nor the 
solicitation of an offer to sell or purchase any investment. Its contents 
are based on information obtained from sources believed to be reliable but 
HSBC makes no representation and accepts no responsibility or liability as 
to its completeness or accuracy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



-
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.

Re: Question to: "No primary artifact to install..."

[Vincent Latombe]

Huh? Is this some kind of predefined profile? I think you got mixed up
Anders ;)


2010/8/26 Anders Hammar 

> mvn install -P release-profile
>
> Should do it.
>
> /Anders (mobile)
>
> Den 2010 8 26 16:13 skrev "Thomas Trepper" :
> > Hi Mathus,
> >
> > thanks a lot for your help. I have updated my pom as you told me and I
> > executed mvn install, which works. Thanks a lot. But it produces only
> > the main jar. But I want to have javadoc, sources, etc also as jars,
> > therefore I executed
> > mvn clean source:jar source:test-jar jar:test-jar javadoc:jar install
> > which now works also fine, it produces all jars as wanted, BUT source,
> > doc, test and test-source are ALSO included in the main-jar, which is
> > *not*, what I want.
> >
> > How can I produce main artifact-jar and additionally (NOT included)
> > javadoc, sources, test and test-sources-jars?
> >
> > Thanks everybody till now,
> >
> > Thomas
> >
> >
> >
> >
> > Am 26.08.2010 16:03, schrieb Baptiste MATHUS:
> >> First, I've simplified the pom your provided.
> >> http://pastebin.com/64XC39VS is totally equivalent for what you put.
> >>
> >> Could you run mvn install and show us the output?
> >>
> >> Thanks
> >>
> >> 2010/8/26 Baptiste MATHUS
> >>
> >>> Specifying that many plugins as you did is just a mean of getting in
> >>> trouble soon.
> >>> Launching a specific plugin, particularly some, with maven is something
> one
> >>> almost never does.
> >>>
> >>> You'd better post here what's the problem running mvn package. This
> should
> >>> work this way, simply.
> >>>
> >>> Using maven the way you show is ant'ish, and it's not getting to the
> point
> >>> where a classical mvn package just package the project, even when not
> >>> knowing anything about your project.
> >>>
> >>> Cheers
> >>>
> >>> 2010/8/26 Thomas Trepper
> >>>
> >>> Yes, I tried that first, but it did not work and during the experiments
> to
>  solve the issue the long commandline arised. Sorry for that, but the
> simple
>  mvn install did not do it either. I will get the same error...
> 
> 
>  Am 26.08.2010 15:12, schrieb Anders Hammar:
> 
>  Why the extremely troublesome mvn command line? Why not just "mvn
> > install"?
> >
> > /Anders
> >
> > On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
> > wrote:
> >
> > Hi all,
> >> this is a snippet from my build, which says, that I have an artifact
> and
> >> attached artifacts, but, whatever I am doing, I always get the
> message:
> >> No
> >> primary artifact to install, installing attached artifacts instead.
> >>
> >> Can anybody point me to the right direction please?
> >>
> >> Thanks a lot and best regards,
> >>
> >> Thomas
> >>
> >> P.S: I start my build from eclipse with the following targets:
> >> clean validate initialize resources:resources compiler:compile
> >> jar:jar
> >> source:jar source:test-jar jar:test-jar javadoc:jar test
> install:install
> >>
> >>
> >>
> >> [INFO]
> >> [INFO] --- maven-install-plugin:2.3:install (default-cli) @
> logging-api
> >> ---
> >> [DEBUG] Created new class realm
> >> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> >> [DEBUG] Populating class realm
> >> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> >> [DEBUG] Included:
> >> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
> >> [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
> >> [DEBUG] Included: junit:junit:jar:3.8.1
> >> [DEBUG] Included: org.codehaus.plexus:plexus-digest:jar:1.0
> >> [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.6
> >> [DEBUG] Excluded:
> >>
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
> >> [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2
> >> [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
> >> [DEBUG] Excluded:
> org.apache.maven:maven-repository-metadata:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.6
> >> [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
> >> [DEBUG] Configuring mojo
> >> 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with
> basic
> >> configurator -->
> >> [DEBUG] (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
> >> [DEBUG] (f) attachedArtifacts =
> >> [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
> >> com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
> >> com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
> >> com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT

Re: Question to: "No primary artifact to install..."

[Anders Hammar]

mvn install -P release-profile

Should do it.

/Anders (mobile)

Den 2010 8 26 16:13 skrev "Thomas Trepper" :
> Hi Mathus,
>
> thanks a lot for your help. I have updated my pom as you told me and I
> executed mvn install, which works. Thanks a lot. But it produces only
> the main jar. But I want to have javadoc, sources, etc also as jars,
> therefore I executed
> mvn clean source:jar source:test-jar jar:test-jar javadoc:jar install
> which now works also fine, it produces all jars as wanted, BUT source,
> doc, test and test-source are ALSO included in the main-jar, which is
> *not*, what I want.
>
> How can I produce main artifact-jar and additionally (NOT included)
> javadoc, sources, test and test-sources-jars?
>
> Thanks everybody till now,
>
> Thomas
>
>
>
>
> Am 26.08.2010 16:03, schrieb Baptiste MATHUS:
>> First, I've simplified the pom your provided.
>> http://pastebin.com/64XC39VS is totally equivalent for what you put.
>>
>> Could you run mvn install and show us the output?
>>
>> Thanks
>>
>> 2010/8/26 Baptiste MATHUS
>>
>>> Specifying that many plugins as you did is just a mean of getting in
>>> trouble soon.
>>> Launching a specific plugin, particularly some, with maven is something
one
>>> almost never does.
>>>
>>> You'd better post here what's the problem running mvn package. This
should
>>> work this way, simply.
>>>
>>> Using maven the way you show is ant'ish, and it's not getting to the
point
>>> where a classical mvn package just package the project, even when not
>>> knowing anything about your project.
>>>
>>> Cheers
>>>
>>> 2010/8/26 Thomas Trepper
>>>
>>> Yes, I tried that first, but it did not work and during the experiments
to
 solve the issue the long commandline arised. Sorry for that, but the
simple
 mvn install did not do it either. I will get the same error...


 Am 26.08.2010 15:12, schrieb Anders Hammar:

 Why the extremely troublesome mvn command line? Why not just "mvn
> install"?
>
> /Anders
>
> On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
> wrote:
>
> Hi all,
>> this is a snippet from my build, which says, that I have an artifact
and
>> attached artifacts, but, whatever I am doing, I always get the
message:
>> No
>> primary artifact to install, installing attached artifacts instead.
>>
>> Can anybody point me to the right direction please?
>>
>> Thanks a lot and best regards,
>>
>> Thomas
>>
>> P.S: I start my build from eclipse with the following targets:
>> clean validate initialize resources:resources compiler:compile
>> jar:jar
>> source:jar source:test-jar jar:test-jar javadoc:jar test
install:install
>>
>>
>>
>> [INFO]
>> [INFO] --- maven-install-plugin:2.3:install (default-cli) @
logging-api
>> ---
>> [DEBUG] Created new class realm
>> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
>> [DEBUG] Populating class realm
>> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
>> [DEBUG] Included:
>> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
>> [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
>> [DEBUG] Included: junit:junit:jar:3.8.1
>> [DEBUG] Included: org.codehaus.plexus:plexus-digest:jar:1.0
>> [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.6
>> [DEBUG] Excluded:
>> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
>> [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2
>> [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
>> [DEBUG] Excluded:
org.apache.maven:maven-repository-metadata:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.6
>> [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
>> [DEBUG] Configuring mojo
>> 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with
basic
>> configurator -->
>> [DEBUG] (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
>> [DEBUG] (f) attachedArtifacts =
>> [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
>> com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
>> com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
>> com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
>> [DEBUG] (f) createChecksum = false
>> [DEBUG] (f) localRepository = id: local
>> url: file:///C:/eclipse-SDK-3.6/maven-repository/
>> layout: none
>>
>> [DEBUG] (f) packaging = jar
>> [DEBUG] (f) pomFile = E:\workspace.utils\logging-api\pom.xml
>> [DEBUG] (f) updateReleaseInfo = false
>> [DEBUG] -- end configuration --
>> [IN

Ear plugin issue

[nishant . raj]

Hi All,

I am trying to get the ear plugin working. 

Followed all the guidelines but could not get it working as its not able 
to "find" the module that I want to package within the ear

It looks for the module in my nexus repository but does not find it.
I have also got the "Resolve workspace project dependencies" enables in 
eclipse.

Pom is attached.

Please advice as I have been struggling with the same for few hrs now.

Thanks
Nishant




HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



-
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Question to: "No primary artifact to install..."

[Thomas Trepper]

 Hi Mathus,

thanks a lot for your help. I have updated my pom as you told me and I 
executed mvn install, which works. Thanks a lot.  But it produces only 
the main jar. But I want to have javadoc, sources, etc also as jars, 
therefore I executed

mvn clean source:jar source:test-jar jar:test-jar javadoc:jar install
which now works also fine, it produces all jars as wanted, BUT source, 
doc, test and test-source are ALSO included in the main-jar, which is 
*not*, what I want.


How can I produce main artifact-jar and additionally (NOT included) 
javadoc, sources, test and test-sources-jars?


Thanks everybody till now,

Thomas




Am 26.08.2010 16:03, schrieb Baptiste MATHUS:

First, I've simplified the pom your provided.
http://pastebin.com/64XC39VS is totally equivalent for what you put.

Could you run mvn install and show us the output?

Thanks

2010/8/26 Baptiste MATHUS


Specifying that many plugins as you did is just a mean of getting in
trouble soon.
Launching a specific plugin, particularly some, with maven is something one
almost never does.

You'd better post here what's the problem running mvn package. This should
work this way, simply.

Using maven the way you show is ant'ish, and it's not getting to the point
where a classical mvn package just package the project, even when not
knowing anything about your project.

Cheers

2010/8/26 Thomas Trepper

  Yes, I tried that first, but it did not work and during the experiments to

solve the issue the long commandline arised. Sorry for that, but the simple
mvn install did not do it either. I will get the same error...


Am 26.08.2010 15:12, schrieb Anders Hammar:

  Why the extremely troublesome mvn command line? Why not just "mvn

install"?

/Anders

On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
wrote:

   Hi all,

this is a snippet from my build, which says, that I have an artifact and
attached artifacts, but, whatever I am doing, I always get the message:
No
primary artifact to install, installing attached artifacts instead.

Can anybody point me to the right direction please?

Thanks a lot and best regards,

Thomas

P.S: I start my build from eclipse with the following targets:
clean validate initialize  resources:resources compiler:compile
  jar:jar
source:jar source:test-jar jar:test-jar javadoc:jar test install:install



[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api
---
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG]   Included:
org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
configurator -->
[DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
[DEBUG]   (f) attachedArtifacts =
[com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
[DEBUG]   (f) createChecksum = false
[DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

[DEBUG]   (f) packaging = jar
[DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] No primary artifact to install, installing attached artifacts
instead.
[INFO] Installing E:\workspace.utils\logging-api\pom.xml to

C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
[INFO] Installing

E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
to

C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
[INFO] Installing

E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
to

C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAP

Re: Question to: "No primary artifact to install..."

[Baptiste MATHUS]

First, I've simplified the pom your provided.
http://pastebin.com/64XC39VS is totally equivalent for what you put.

Could you run mvn install and show us the output?

Thanks

2010/8/26 Baptiste MATHUS 

> Specifying that many plugins as you did is just a mean of getting in
> trouble soon.
> Launching a specific plugin, particularly some, with maven is something one
> almost never does.
>
> You'd better post here what's the problem running mvn package. This should
> work this way, simply.
>
> Using maven the way you show is ant'ish, and it's not getting to the point
> where a classical mvn package just package the project, even when not
> knowing anything about your project.
>
> Cheers
>
> 2010/8/26 Thomas Trepper 
>
>  Yes, I tried that first, but it did not work and during the experiments to
>> solve the issue the long commandline arised. Sorry for that, but the simple
>> mvn install did not do it either. I will get the same error...
>>
>>
>> Am 26.08.2010 15:12, schrieb Anders Hammar:
>>
>>  Why the extremely troublesome mvn command line? Why not just "mvn
>>> install"?
>>>
>>> /Anders
>>>
>>> On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
>>> wrote:
>>>
>>>   Hi all,

 this is a snippet from my build, which says, that I have an artifact and
 attached artifacts, but, whatever I am doing, I always get the message:
 No
 primary artifact to install, installing attached artifacts instead.

 Can anybody point me to the right direction please?

 Thanks a lot and best regards,

 Thomas

 P.S: I start my build from eclipse with the following targets:
clean validate initialize  resources:resources compiler:compile
  jar:jar
 source:jar source:test-jar jar:test-jar javadoc:jar test install:install



 [INFO]
 [INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api
 ---
 [DEBUG] Created new class realm
 plugin>org.apache.maven.plugins:maven-install-plugin:2.3
 [DEBUG] Populating class realm
 plugin>org.apache.maven.plugins:maven-install-plugin:2.3
 [DEBUG]   Included:
 org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
 [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
 [DEBUG]   Included: junit:junit:jar:3.8.1
 [DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
 [DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
 [DEBUG]   Excluded:
 org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
 [DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
 [DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
 [DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
 [DEBUG] Configuring mojo
 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
 configurator -->
 [DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
 [DEBUG]   (f) attachedArtifacts =
 [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
 com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
 com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
 com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
 [DEBUG]   (f) createChecksum = false
 [DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

 [DEBUG]   (f) packaging = jar
 [DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
 [DEBUG]   (f) updateReleaseInfo = false
 [DEBUG] -- end configuration --
 [INFO] No primary artifact to install, installing attached artifacts
 instead.
 [INFO] Installing E:\workspace.utils\logging-api\pom.xml to

 C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
 [INFO] Installing

 E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
 to

 C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
 [INFO] Installing

 E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
 to

 C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
 [INFO] Installing

 E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
 to

 C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-S

Re: Question to: "No primary artifact to install..."

[Baptiste MATHUS]

Specifying that many plugins as you did is just a mean of getting in trouble
soon.
Launching a specific plugin, particularly some, with maven is something one
almost never does.

You'd better post here what's the problem running mvn package. This should
work this way, simply.

Using maven the way you show is ant'ish, and it's not getting to the point
where a classical mvn package just package the project, even when not
knowing anything about your project.

Cheers

2010/8/26 Thomas Trepper 

>  Yes, I tried that first, but it did not work and during the experiments to
> solve the issue the long commandline arised. Sorry for that, but the simple
> mvn install did not do it either. I will get the same error...
>
>
> Am 26.08.2010 15:12, schrieb Anders Hammar:
>
>  Why the extremely troublesome mvn command line? Why not just "mvn
>> install"?
>>
>> /Anders
>>
>> On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
>> wrote:
>>
>>   Hi all,
>>>
>>> this is a snippet from my build, which says, that I have an artifact and
>>> attached artifacts, but, whatever I am doing, I always get the message:
>>> No
>>> primary artifact to install, installing attached artifacts instead.
>>>
>>> Can anybody point me to the right direction please?
>>>
>>> Thanks a lot and best regards,
>>>
>>> Thomas
>>>
>>> P.S: I start my build from eclipse with the following targets:
>>>clean validate initialize  resources:resources compiler:compile
>>>  jar:jar
>>> source:jar source:test-jar jar:test-jar javadoc:jar test install:install
>>>
>>>
>>>
>>> [INFO]
>>> [INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api
>>> ---
>>> [DEBUG] Created new class realm
>>> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
>>> [DEBUG] Populating class realm
>>> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
>>> [DEBUG]   Included:
>>> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
>>> [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
>>> [DEBUG]   Included: junit:junit:jar:3.8.1
>>> [DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
>>> [DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
>>> [DEBUG]   Excluded:
>>> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
>>> [DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
>>> [DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
>>> [DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
>>> configurator -->
>>> [DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
>>> [DEBUG]   (f) attachedArtifacts =
>>> [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
>>> com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
>>> com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
>>> com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
>>> [DEBUG]   (f) createChecksum = false
>>> [DEBUG]   (f) localRepository =id: local
>>>  url: file:///C:/eclipse-SDK-3.6/maven-repository/
>>>   layout: none
>>>
>>> [DEBUG]   (f) packaging = jar
>>> [DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
>>> [DEBUG]   (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] No primary artifact to install, installing attached artifacts
>>> instead.
>>> [INFO] Installing E:\workspace.utils\logging-api\pom.xml to
>>>
>>> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
>>> [INFO] Installing
>>>
>>> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
>>> to
>>>
>>> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
>>> [INFO] Installing
>>>
>>> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
>>> to
>>>
>>> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
>>> [INFO] Installing
>>>
>>> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
>>> to
>>>
>>> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
>>> [INFO] Installing
>>>
>>> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-javadoc.jar
>>> to
>>>
>>> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-javadoc.jar
>>> [INFO]
>>> ---

Re: Question to: "No primary artifact to install..."

[Thomas Trepper]

 Yes, I tried that first, but it did not work and during the 
experiments to solve the issue the long commandline arised. Sorry for 
that, but the simple mvn install did not do it either. I will get the 
same error...



Am 26.08.2010 15:12, schrieb Anders Hammar:

Why the extremely troublesome mvn command line? Why not just "mvn install"?

/Anders

On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
wrote:


  Hi all,

this is a snippet from my build, which says, that I have an artifact and
attached artifacts, but, whatever I am doing, I always get the message: No
primary artifact to install, installing attached artifacts instead.

Can anybody point me to the right direction please?

Thanks a lot and best regards,

Thomas

P.S: I start my build from eclipse with the following targets:
clean validate initialize  resources:resources compiler:compile  jar:jar
source:jar source:test-jar jar:test-jar javadoc:jar test install:install



[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api ---
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG]   Included:
org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
configurator -->
[DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
[DEBUG]   (f) attachedArtifacts =
[com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
[DEBUG]   (f) createChecksum = false
[DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

[DEBUG]   (f) packaging = jar
[DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] No primary artifact to install, installing attached artifacts
instead.
[INFO] Installing E:\workspace.utils\logging-api\pom.xml to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-javadoc.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-javadoc.jar
[INFO]

[INFO] BUILD SUCCESS
[INFO]



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Question to: "No primary artifact to install..."

[Anders Hammar]

Why the extremely troublesome mvn command line? Why not just "mvn install"?

/Anders

On Thu, Aug 26, 2010 at 14:20, Thomas Trepper
wrote:

>  Hi all,
>
> this is a snippet from my build, which says, that I have an artifact and
> attached artifacts, but, whatever I am doing, I always get the message: No
> primary artifact to install, installing attached artifacts instead.
>
> Can anybody point me to the right direction please?
>
> Thanks a lot and best regards,
>
> Thomas
>
> P.S: I start my build from eclipse with the following targets:
>clean validate initialize  resources:resources compiler:compile  jar:jar
> source:jar source:test-jar jar:test-jar javadoc:jar test install:install
>
>
>
> [INFO]
> [INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api ---
> [DEBUG] Created new class realm
> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> [DEBUG] Populating class realm
> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> [DEBUG]   Included:
> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
> [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
> [DEBUG]   Included: junit:junit:jar:3.8.1
> [DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
> [DEBUG]   Excluded:
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
> [DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
> [DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
> configurator -->
> [DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
> [DEBUG]   (f) attachedArtifacts =
> [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
> [DEBUG]   (f) createChecksum = false
> [DEBUG]   (f) localRepository =id: local
>  url: file:///C:/eclipse-SDK-3.6/maven-repository/
>   layout: none
>
> [DEBUG]   (f) packaging = jar
> [DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
> [DEBUG]   (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] No primary artifact to install, installing attached artifacts
> instead.
> [INFO] Installing E:\workspace.utils\logging-api\pom.xml to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-javadoc.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-javadoc.jar
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Multiple profile execution in maven

[Anders Hammar]

I checked the docs at maven.apache.org and they say comma list. But as
always, there might be bugs...:-)

/Anders

On Thu, Aug 26, 2010 at 14:42, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I think you use multiple -P's to activate them
>
> -Px -Py
>
> but that could all just be my imagination ;-)
>
> On 26 August 2010 12:33, Anders Hammar  wrote:
>
> > It should work. However, I'm not sure if I have ever enabled more than
> one
> > profile from command line.
> > Just for the heck of it, could you try adding a space between -P and the
> > profiles list ("-P x,y")?
> >
> > /Anders
> >
> > On Thu, Aug 26, 2010 at 13:16, Sridhar Laxmipuram Srinivasan <
> > sridh...@yahoo-inc.com> wrote:
> >
> > > Hi,
> > > I have 2 profiles which are deactivated by default but at run time I
> need
> > > to execute both of them, I have tried with -P, but of no use it
> > always
> > > executes the latter, Could you kindly provide me a solution to this. I
> am
> > > using maven 2.2.1 version
> > >
> > > thnkx
> > > sridharl
> > >
> > >
> >
>

Re: Multiple profile execution in maven

[nishant . raj]

You can use a comma separated list -Px,y





Stephen Connolly  
Aug 26 2010 13:43

Mail Size: 6227

Please respond to
"Maven Users List" 


To
Maven Users List 
cc

Subject
Re: Multiple profile execution in maven

  Entity
   HSBC Bank plc - HBEU



I think you use multiple -P's to activate them

-Px -Py

but that could all just be my imagination ;-)

On 26 August 2010 12:33, Anders Hammar  wrote:

> It should work. However, I'm not sure if I have ever enabled more than 
one
> profile from command line.
> Just for the heck of it, could you try adding a space between -P and the
> profiles list ("-P x,y")?
>
> /Anders
>
> On Thu, Aug 26, 2010 at 13:16, Sridhar Laxmipuram Srinivasan <
> sridh...@yahoo-inc.com> wrote:
>
> > Hi,
> > I have 2 profiles which are deactivated by default but at run time I 
need
> > to execute both of them, I have tried with -P, but of no use it
> always
> > executes the latter, Could you kindly provide me a solution to this. I 
am
> > using maven 2.2.1 version
> >
> > thnkx
> > sridharl
> >
> >
>




HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



-
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.

Re: Multiple profile execution in maven

[Stephen Connolly]

I think you use multiple -P's to activate them

-Px -Py

but that could all just be my imagination ;-)

On 26 August 2010 12:33, Anders Hammar  wrote:

> It should work. However, I'm not sure if I have ever enabled more than one
> profile from command line.
> Just for the heck of it, could you try adding a space between -P and the
> profiles list ("-P x,y")?
>
> /Anders
>
> On Thu, Aug 26, 2010 at 13:16, Sridhar Laxmipuram Srinivasan <
> sridh...@yahoo-inc.com> wrote:
>
> > Hi,
> > I have 2 profiles which are deactivated by default but at run time I need
> > to execute both of them, I have tried with -P, but of no use it
> always
> > executes the latter, Could you kindly provide me a solution to this. I am
> > using maven 2.2.1 version
> >
> > thnkx
> > sridharl
> >
> >
>

Re: Correcting a groupID

[Stephen Connolly]

Why not have commons-net:commons-net become an empty jar which has a
dependency on org.apache.commons:net

that way, anyone with the old GA coords will just have an empty jar on their
classpath and the correct jar as well

On 26 August 2010 00:13, Benson Margulies  wrote:

> Let me recap the pain scenario here:
>
> Existing poms reference commons-net under the old group ID.
>
> commons-net releases a new version under a new group ID.
>
> Dependencies under the old group ID won't be seen as 'the same thing'
> as the new group ID, so
>
> a project that references the new group ID and has a dependency that
> uses the old group ID gets both in the classpath, and probably
> experiences chaos until repaired with exclusions.
>
> Unless maven grew a feature whereby the new artifact could explicitly
> declare itself a successor of the old one under the other name, this
> is unavoidable. Either don't rename or live with this as an annoyance
> to the users of the new version. Renaming packages might help, insofar
> as the two versions might then coexist happily.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Question to: "No primary artifact to install..."

[Thomas Trepper]

 Hi Brian,

I am sorry, I do not know, you you exactly mean.  For me it is a 
problem, because maven does not install my main artifact:  
com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT


Following is my pom:
http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

4.0.0
com.blueclaim
logging-api
jar
0.0.4-SNAPSHOT
logging-api
logging
http://maven.apache.org

src/main/java
src/test/java
target
target


org.apache.maven.plugins
maven-resources-plugin

UTF-8



org.apache.maven.plugins
maven-compiler-plugin


1.6
1.6



org.apache.maven.plugins
maven-javadoc-plugin


org.apache.maven.plugins
maven-source-plugin



org.apache.maven.plugins
maven-jar-plugin
2.3.1




com.blueclaim.logging-api

logging-api
${project.version}
"blueclaim.com"







org.apache.maven.plugins
maven-javadoc-plugin



org.apache.maven.plugins
maven-release-plugin


org.apache.maven.plugins
maven-antrun-plugin


generate-version-info

run

process-sources









org.apache.maven.plugins
maven-install-plugin
2.3.1





org.jdom
jdom
1.1


junit
junit
3.8.1
test


com.blueclaim
commons
0.0.1



UTF-8




Thanks lot for any hint

Thomas










Am 26.08.2010 14:30, schrieb Brian Fox:

this means you have no artifact with an empty classifier. This is not
necessarily a problem, if you're using the build helper or assembly to
build attached artifacts.

On Thu, Aug 26, 2010 at 8:20 AM, Thomas Trepper
  wrote:

  Hi all,

this is a snippet from my build, which says, that I have an artifact and
attached artifacts, but, whatever I am doing, I always get the message: No
primary artifact to install, installing attached artifacts instead.

Can anybody point me to the right direction please?

Thanks a lot and best regards,

Thomas

P.S: I start my build from eclipse with the following targets:
  clean validate initialize  resources:resources compiler:compile  jar:jar
source:jar source:test-jar jar:test-jar javadoc:jar test install:install



[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api ---
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG]   Included:
org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
configurator -->
[DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
[DEBUG]   (f) attachedArtifacts =
[com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
[DEBUG]   (f) createChecksum = false
[DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

[DEBUG]   (f) packaging = jar
[DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] No primary artifact to install, installing attached artifacts
instead.
[INFO] Installing E:\workspace.utils\logging-api\pom.xml to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
[INFO] Installing
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
to
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
[INFO] 

Re: Correcting a groupID

[Ron Wheeler]

 On 26/08/2010 8:10 AM, sebb wrote:

On 26 August 2010 12:42, Ron Wheeler  wrote:

  On 25/08/2010 7:13 PM, Benson Margulies wrote:

Let me recap the pain scenario here:

Existing poms reference commons-net under the old group ID.

commons-net releases a new version under a new group ID.

Dependencies under the old group ID won't be seen as 'the same thing'
as the new group ID, so

a project that references the new group ID and has a dependency that
uses the old group ID gets both in the classpath, and probably
experiences chaos until repaired with exclusions.
Unless maven grew a feature whereby the new artifact could explicitly
declare itself a successor of the old one under the other name, this
is unavoidable. Either don't rename or live with this as an annoyance
to the users of the new version. Renaming packages might help, insofar
as the two versions might then coexist happily.

A way to deal with this is to do what we do at the application level and use
aggregate POMs to specify dependencies on third party software.
Once we shift to the new version with the new group id, we will have to add
an exclusion to each of our aggregation POMs to prevent third party packages
from pulling in the old group id.

But again, this is extra work for the user.
But it is only 1 or 2 POMs to look at and possibly change rather than 60 
and we will not get caught up in the problem by accident.

It also affects only 1 person not the whole team.

We still have to be mindful of the issue when upgrading a version of a 
third party library or adding a new one. It is hard to detect.

I'll say it again - unless and until Maven can transparently handle
such changes, getting the groupId etc correct in the first place is
very important, especially for libraries.
It does look like something that Maven should handle since there appears 
to be a lot of effort to clean up groupIds at Apache and other places.
This will only get worse as Maven gets more popular and projects that 
were early into Maven start to improve their groupId structure.



Ron


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Question to: "No primary artifact to install..."

[Brian Fox]

this means you have no artifact with an empty classifier. This is not
necessarily a problem, if you're using the build helper or assembly to
build attached artifacts.

On Thu, Aug 26, 2010 at 8:20 AM, Thomas Trepper
 wrote:
>  Hi all,
>
> this is a snippet from my build, which says, that I have an artifact and
> attached artifacts, but, whatever I am doing, I always get the message: No
> primary artifact to install, installing attached artifacts instead.
>
> Can anybody point me to the right direction please?
>
> Thanks a lot and best regards,
>
> Thomas
>
> P.S: I start my build from eclipse with the following targets:
>  clean validate initialize  resources:resources compiler:compile  jar:jar
> source:jar source:test-jar jar:test-jar javadoc:jar test install:install
>
>
>
> [INFO]
> [INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api ---
> [DEBUG] Created new class realm
> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> [DEBUG] Populating class realm
> plugin>org.apache.maven.plugins:maven-install-plugin:2.3
> [DEBUG]   Included:
> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3
> [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
> [DEBUG]   Included: junit:junit:jar:3.8.1
> [DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
> [DEBUG]   Excluded:
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
> [DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
> [DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic
> configurator -->
> [DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
> [DEBUG]   (f) attachedArtifacts =
> [com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT,
> com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]
> [DEBUG]   (f) createChecksum = false
> [DEBUG]   (f) localRepository =        id: local
>      url: file:///C:/eclipse-SDK-3.6/maven-repository/
>   layout: none
>
> [DEBUG]   (f) packaging = jar
> [DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
> [DEBUG]   (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] No primary artifact to install, installing attached artifacts
> instead.
> [INFO] Installing E:\workspace.utils\logging-api\pom.xml to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
> [INFO] Installing
> E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-javadoc.jar
> to
> C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-javadoc.jar
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Question to: "No primary artifact to install..."

[Thomas Trepper]

 Hi all,

this is a snippet from my build, which says, that I have an artifact and 
attached artifacts, but, whatever I am doing, I always get the message: 
No primary artifact to install, installing attached artifacts instead.


Can anybody point me to the right direction please?

Thanks a lot and best regards,

Thomas

P.S: I start my build from eclipse with the following 
targets:clean validate initialize  resources:resources 
compiler:compile  jar:jar source:jar source:test-jar jar:test-jar 
javadoc:jar test install:install




[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-cli) @ logging-api ---
[DEBUG] Created new class realm 
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG] Populating class realm 
plugin>org.apache.maven.plugins:maven-install-plugin:2.3
[DEBUG]   Included: 
org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3

[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-digest:jar:1.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded: 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1

[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-install-plugin:2.3:install' with basic 
configurator -->

[DEBUG]   (f) artifact = com.blueclaim:logging-api:jar:0.0.4-SNAPSHOT
[DEBUG]   (f) attachedArtifacts = 
[com.blueclaim:logging-api:java-source:sources:0.0.4-SNAPSHOT, 
com.blueclaim:logging-api:java-source:test-sources:0.0.4-SNAPSHOT, 
com.blueclaim:logging-api:test-jar:tests:0.0.4-SNAPSHOT, 
com.blueclaim:logging-api:javadoc:javadoc:0.0.4-SNAPSHOT]

[DEBUG]   (f) createChecksum = false
[DEBUG]   (f) localRepository =id: local
  url: file:///C:/eclipse-SDK-3.6/maven-repository/
   layout: none

[DEBUG]   (f) packaging = jar
[DEBUG]   (f) pomFile = E:\workspace.utils\logging-api\pom.xml
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] No primary artifact to install, installing attached artifacts 
instead.
[INFO] Installing E:\workspace.utils\logging-api\pom.xml to 
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT.pom
[INFO] Installing 
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-sources.jar 
to 
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-sources.jar
[INFO] Installing 
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-test-sources.jar 
to 
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-test-sources.jar
[INFO] Installing 
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-tests.jar 
to 
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-tests.jar
[INFO] Installing 
E:\workspace.utils\logging-api\target\logging-api-0.0.4-SNAPSHOT-javadoc.jar 
to 
C:\eclipse-SDK-3.6\maven-repository\com\blueclaim\logging-api\0.0.4-SNAPSHOT\logging-api-0.0.4-SNAPSHOT-javadoc.jar
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Correcting a groupID

[sebb]

On 26 August 2010 12:42, Ron Wheeler  wrote:
>  On 25/08/2010 7:13 PM, Benson Margulies wrote:
>>
>> Let me recap the pain scenario here:
>>
>> Existing poms reference commons-net under the old group ID.
>>
>> commons-net releases a new version under a new group ID.
>>
>> Dependencies under the old group ID won't be seen as 'the same thing'
>> as the new group ID, so
>>
>> a project that references the new group ID and has a dependency that
>> uses the old group ID gets both in the classpath, and probably
>> experiences chaos until repaired with exclusions.
>
>> Unless maven grew a feature whereby the new artifact could explicitly
>> declare itself a successor of the old one under the other name, this
>> is unavoidable. Either don't rename or live with this as an annoyance
>> to the users of the new version. Renaming packages might help, insofar
>> as the two versions might then coexist happily.
>
> A way to deal with this is to do what we do at the application level and use
> aggregate POMs to specify dependencies on third party software.
> Once we shift to the new version with the new group id, we will have to add
> an exclusion to each of our aggregation POMs to prevent third party packages
> from pulling in the old group id.

But again, this is extra work for the user.

I'll say it again - unless and until Maven can transparently handle
such changes, getting the groupId etc correct in the first place is
very important, especially for libraries.

>
> Ron
>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven parent classpath issues

[Aleksey Didik]

 Hello.

Use ${basedir}/src/main/jibx/customization.xml instead your variant.

By default work directory is a directory when you start mvn.
Always use ${basedir} before you relative file paths.

hth,
Aleksey.

26.08.2010 15:51, nishant@hsbcib.com ?:

src/main/jibx/customization.xml f

Re: Maven parent classpath issues

[Anders Hammar]

I'm guessing that you have the plugin bound in the parent pom. Move it to
the child project and you should be fine.

/Anders

On Thu, Aug 26, 2010 at 13:51,  wrote:

>
> Hi All,
>
> I am trying to build a project hierarchy.
>
> The structure looks something like this,
>
>
> RootProject (Pom packaging)
>
> Child Project (jar packaging)
>
> The child project uses a plugin which uses src/main/jibx/customization.xml
> file
>
> I can build the child project independently. The problem is that when I try
> to build it from the parent project it says file not found
> (src/main/jibx/customization.xml )
>
> The parent seems to be looking for the file in its own folder structure
> rather than delegating packaging execution to child.
>
> Please could somebody help.
>
> Both poms are attached.
>
> Thanks
> Nishant
>
>
>
>
> 
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> 
>  - SAVE PAPER - THINK BEFORE YOU
> PRINT! This transmission has been issued by a member of the HSBC Group
> "HSBC" for the information of the addressee only and should not be
> reproduced and/or distributed to any other person. Each page attached hereto
> must be read in conjunction with any disclaimer which forms part of it.
> Unless otherwise stated, this transmission is neither an offer nor the
> solicitation of an offer to sell or purchase any investment. Its contents
> are based on information obtained from sources believed to be reliable but
> HSBC makes no representation and accepts no responsibility or liability as
> to its completeness or accuracy.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

Re: nexus, local repository, and m2eclipse

[Marshall Schor]

 Maybe a good idea is to put a pointer to the nexus list in the most obvious
place(s) people would look in the Maven on-line docs, saying something like "for
questions about Nexus, please post to the Nexus mailing list(s) found here". 
That way, users would get "just in time" education :-).

-Marshall Schor

On 8/23/2010 4:02 PM, Wayne Fay wrote:
>> I didn't know there was a nexus list.  Thanks.
> This happens often. I don't know why there is such confusion. Perhaps
> the Sonatype folks need to make this more obvious somewhere on the
> Nexus site?
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven parent classpath issues

[nishant . raj]

Hi All,

I am trying to build a project hierarchy.

The structure looks something like this,


RootProject (Pom packaging)

Child Project (jar packaging)

The child project uses a plugin which uses src/main/jibx/customization.xml 
file

I can build the child project independently. The problem is that when I 
try to build it from the parent project it says file not found 
(src/main/jibx/customization.xml )

The parent seems to be looking for the file in its own folder structure 
rather than delegating packaging execution to child.

Please could somebody help.

Both poms are attached.

Thanks
Nishant





HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority



-
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Correcting a groupID

[Ron Wheeler]

 On 25/08/2010 7:13 PM, Benson Margulies wrote:

Let me recap the pain scenario here:

Existing poms reference commons-net under the old group ID.

commons-net releases a new version under a new group ID.

Dependencies under the old group ID won't be seen as 'the same thing'
as the new group ID, so

a project that references the new group ID and has a dependency that
uses the old group ID gets both in the classpath, and probably
experiences chaos until repaired with exclusions.



Unless maven grew a feature whereby the new artifact could explicitly
declare itself a successor of the old one under the other name, this
is unavoidable. Either don't rename or live with this as an annoyance
to the users of the new version. Renaming packages might help, insofar
as the two versions might then coexist happily.


A way to deal with this is to do what we do at the application level and 
use aggregate POMs to specify dependencies on third party software.
Once we shift to the new version with the new group id, we will have to 
add an exclusion to each of our aggregation POMs to prevent third party 
packages from pulling in the old group id.


Ron


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multiple profile execution in maven

[Anders Hammar]

It should work. However, I'm not sure if I have ever enabled more than one
profile from command line.
Just for the heck of it, could you try adding a space between -P and the
profiles list ("-P x,y")?

/Anders

On Thu, Aug 26, 2010 at 13:16, Sridhar Laxmipuram Srinivasan <
sridh...@yahoo-inc.com> wrote:

> Hi,
> I have 2 profiles which are deactivated by default but at run time I need
> to execute both of them, I have tried with -P, but of no use it always
> executes the latter, Could you kindly provide me a solution to this. I am
> using maven 2.2.1 version
>
> thnkx
> sridharl
>
>

Multiple profile execution in maven

[Sridhar Laxmipuram Srinivasan]

Hi,
I have 2 profiles which are deactivated by default but at run time I need to 
execute both of them, I have tried with -P, but of no use it always 
executes the latter, Could you kindly provide me a solution to this. I am using 
maven 2.2.1 version

thnkx
sridharl

parent pom installed/deployed additional "{$project.artifactId}-${project.version}-site.xml" artefact

[Oleg Estekhin]

 Hi

I have a multi-module project with a parent module and three child 
modules. On deployment the parent module somehow produced additional 
"{$project.artifactId}-${project.version}-site.xml" artefact which got 
installed and deployed along with the parent module's pom. The contents 
of that -site.xml correspond to the parent's src/site/site.xml 
descriptor, but why is this file installed/deployed as a project artifact?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org