Re: Arranging Modules on the File System
Wow, thanks for the awesome tip! That's has helped clear things up enourmously. It was actually fairly simple to flatten the Maven modules the way I suspected. It was vastly more difficult to 'flatten' the Eclipse projects in the file system - well actually it was easy to flatten the Eclipse projects, it was really difficult to figure out how. Also, the reference you gave me has tons more considerations on dealing with Maven in Jazz-land. Cheers, Eric On 2011-04-18 5:38 PM, Barrie Treloar wrote: On Tue, Apr 19, 2011 at 8:17 AM, Eric Kolotyluk wrote: I apologize if this is a newbie question, but I'm looking for a quick answer... I'm using Sonatype Maven plug-in for Eclipse and I have set up a project with several modules. The way the plug-in arranged them on the file system is: You may have better luck on the m2e mailing list, or ask the Team Concert lists how a hierarchical layout is supported. You may be able to use the guidance at http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html *Read this carefully* Especially "Note, you have to delete the .project-file of your parent project before." You need to do this as the "import" step will produce a blank list of projects to import, but if you delete the .project file and try the sub-projects are now available in the list. Eclipse doesn't really support "projects within projects" so your mileage may vary", however a lot of us have this working ok. You can also try turning off Team support for the sub-projects and only uses the main project for checkin/checkout. - 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: Dynamically generating class names with archetype
On 04/19/2011 11:11 PM, Rick Genter wrote:
> I'm building an archetype for generating Maven projects for our
> custom application framework. Everything is working but the generated
> project always has the same class names and annotations. I would like
> to be able to dynamically specify those names/annotations.
[...]
> but what I'd like to do is something like this:
>
> package ${packageName};
>
> // imports go here...
>
> @OurAnnotation(client="${client}", application="${clientApp}",
> version="${clientAppVersion}") public class ${clientApp} extends
> OurBaseClass { ... }
>
> I tried the above and using:
>
> mvn archetype:generate -DarchetypeGroupId=...
> -DarchetypeArtifactId=... -DarchetypeVersion=... -Dclient=Acme
> -DclientApp=HelloWorld6 -DclientAppVersion=1.0.0-SNAPSHOT
> -DgroupId=net.interactions.example -Dversion=0.0.1-SNAPSHOT
> -DartifactId=hello-world-6
>
> my generated ClientApp.java file had the correct package name
> (net.interactions.example), but none of the other substitutions were
> performed. Also, I'd need the generated file itself to have the
> correct name (${clientApp}.java). I'd have preferred that the
> generated file be named "HelloWorld6.java" and have the content:
Yes this is possible. Name the Java class in the archetype
__clientApp__.java and the archetype should fill in the proper variable
name. You need to specify the clientApp property in the
archetype-metadata.xml to enable the substitution.
-dirk
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
surefire build from trunk?
I want to test a recent bugfix committed to the surefire trunk. There appear to be continuous builds running of the trunk but I don't see any way to get the actual build artifacts from them? How can I get a jar built from the most recent revision of surefire trunk?
Re: Dynamically generating class names with archetype
At the top of that page there is a link to a new archetype descriptor. Have a look there. On Apr 19, 2011 6:14 PM, "Rick Genter" wrote: > On Apr 19, 2011, at 3:05 PM, Ryan Connolly wrote: > >> Hi have you defined these properties in an archetype descriptor? >> >> http://maven.apache.org/guides/mini/guide-creating-archetypes.html > > According to the documentation at: > > http://maven.apache.org/archetype/archetype-common/archetype.html > > the only elements supported by are , , , , , and . Where would I put the definitions of those properties? > > -- > Rick Genter > rgen...@interactions.net > > > > *** > This e-mail and any of its attachments may contain Interactions Corporation > proprietary information, which is privileged, confidential, or subject to > copyright belonging to the Interactions Corporation. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If you > are not the intended recipient of this e-mail, you are hereby notified that any > dissemination, distribution, copying, or action taken in relation to the > contents of and attachments to this e-mail is strictly prohibited and may be > unlawful. If you have received this e-mail in error, please notify the sender > immediately and permanently delete the original and any copy of this e-mail and > any printout. Thank You. > *** > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: Dynamically generating class names with archetype
On Apr 19, 2011, at 3:05 PM, Ryan Connolly wrote: > Hi have you defined these properties in an archetype descriptor? > > http://maven.apache.org/guides/mini/guide-creating-archetypes.html According to the documentation at: http://maven.apache.org/archetype/archetype-common/archetype.html the only elements supported by are , , , , , and . Where would I put the definitions of those properties? -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dynamically generating class names with archetype
Hi have you defined these properties in an archetype descriptor?
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
On Apr 19, 2011 5:11 PM, "Rick Genter" wrote:
> I'm building an archetype for generating Maven projects for our custom
application framework. Everything is working but the generated project
always has the same class names and annotations. I would like to be able to
dynamically specify those names/annotations.
>
> For example, I can specify my Java file
(src/main/resources/archetype-resources/src/main/java/ClientApp.java) like
this:
>
> package ${packageName};
>
> // imports go here...
>
> @OurAnnotation(client="Client", application="ClientApp",
version="1.0.0-SNAPSHOT")
> public class ClientApp extends OurBaseClass {
> ...
> }
>
> but what I'd like to do is something like this:
>
> package ${packageName};
>
> // imports go here...
>
> @OurAnnotation(client="${client}", application="${clientApp}",
version="${clientAppVersion}")
> public class ${clientApp} extends OurBaseClass {
> ...
> }
>
> I tried the above and using:
>
> mvn archetype:generate -DarchetypeGroupId=... -DarchetypeArtifactId=...
-DarchetypeVersion=... -Dclient=Acme -DclientApp=HelloWorld6
-DclientAppVersion=1.0.0-SNAPSHOT -DgroupId=net.interactions.example
-Dversion=0.0.1-SNAPSHOT -DartifactId=hello-world-6
>
> my generated ClientApp.java file had the correct package name
(net.interactions.example), but none of the other substitutions were
performed. Also, I'd need the generated file itself to have the correct name
(${clientApp}.java). I'd have preferred that the generated file be named
"HelloWorld6.java" and have the content:
>
> package net.interactions.example;
>
> // imports go here...
>
> @OurAnnotation(client="Acme", application="HelloWorld6",
version="0.0.1-SNAPSHOT")
> public class HelloWorld6 extends OurBaseClass {
> ...
> }
>
>
> Is what I want to do possible?
> --
> Rick Genter
> rgen...@interactions.net
>
>
>
>
***
> This e-mail and any of its attachments may contain Interactions
Corporation
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to the Interactions Corporation. This e-mail is
intended
> solely for the use of the individual or entity to which it is addressed.
If you
> are not the intended recipient of this e-mail, you are hereby notified
that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this e-mail is strictly prohibited and may
be
> unlawful. If you have received this e-mail in error, please notify the
sender
> immediately and permanently delete the original and any copy of this
e-mail and
> any printout. Thank You.
>
***
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
Dynamically generating class names with archetype
I'm building an archetype for generating Maven projects for our custom
application framework. Everything is working but the generated project always
has the same class names and annotations. I would like to be able to
dynamically specify those names/annotations.
For example, I can specify my Java file
(src/main/resources/archetype-resources/src/main/java/ClientApp.java) like this:
package ${packageName};
// imports go here...
@OurAnnotation(client="Client", application="ClientApp",
version="1.0.0-SNAPSHOT")
public class ClientApp extends OurBaseClass {
...
}
but what I'd like to do is something like this:
package ${packageName};
// imports go here...
@OurAnnotation(client="${client}", application="${clientApp}",
version="${clientAppVersion}")
public class ${clientApp} extends OurBaseClass {
...
}
I tried the above and using:
mvn archetype:generate -DarchetypeGroupId=... -DarchetypeArtifactId=...
-DarchetypeVersion=... -Dclient=Acme -DclientApp=HelloWorld6
-DclientAppVersion=1.0.0-SNAPSHOT -DgroupId=net.interactions.example
-Dversion=0.0.1-SNAPSHOT -DartifactId=hello-world-6
my generated ClientApp.java file had the correct package name
(net.interactions.example), but none of the other substitutions were performed.
Also, I'd need the generated file itself to have the correct name
(${clientApp}.java). I'd have preferred that the generated file be named
"HelloWorld6.java" and have the content:
package net.interactions.example;
// imports go here...
@OurAnnotation(client="Acme", application="HelloWorld6",
version="0.0.1-SNAPSHOT")
public class HelloWorld6 extends OurBaseClass {
...
}
Is what I want to do possible?
--
Rick Genter
rgen...@interactions.net
***
This e-mail and any of its attachments may contain Interactions Corporation
proprietary information, which is privileged, confidential, or subject to
copyright belonging to the Interactions Corporation. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If you
are not the intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this e-mail is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this e-mail and
any printout. Thank You.
***
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven and Subversion.
$ svn propget svn:externals calc
third-party/sounds http://sounds.red-bean.com/repos
third-party/skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker
sounds
Repository for sounds
http://sounds.red-bean.com/repos
default
always
toolkit
Repository for sounds-toolkit revision 21
http://sounds.red-bean.com/repos/skin-marker
default
always
sounds
false
${pom.artifactId}
sounds
...
...
sounds
...
...
...
...
...
toolkit
false
${pom.artifactId}
toolkit
...
...
toolkit
...
...
...
...
...
the point is you dont want to have to avert any special repository commands to
accomodate different versioned
artifacts located in different repositories
makes sense?
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Tue, 19 Apr 2011 20:56:28 +0200
> Subject: Re: Maven and Subversion.
> From: bsmith.o...@gmail.com
> To: users@maven.apache.org
>
> On Tue, Apr 19, 2011 at 20:38, wrote:
> > I am wondering if anyone has a good solution to the following issue.
> >
> > I have a multi module maven configuration ( a pom that runs multiple poms
> > underneath it.). I made it a multi module project because the sub projects
> > are very similar and it is convenient to run them all from one pom.
> > However, I need each of these sub projects to be versioned independently.
> > In subversion, you need to make trunk, tags, and branches folders for each
> > project to do this. This breaks the multi module directory structure for
> > Maven as it requires the pom to be in the top level folder for each of the
> > sub projects.
> >
> > Does anyone have a solution as to the best way to make this work, or am I
> > stuck with not using the multi module project in Maven?
> >
> > Thanks,
> >
> > Todd
>
> In our repository we have the policy that only modules that are always
> released together can live in the same trunk. As a result we don't
> have many multi-module builds. This isn't all rainbows and unicorns,
> as this means more individual trunks to tag, more versions to keep
> track of, more things to build and deploy etc.
>
> For such cases, we've used svn:externals to pull together a few large
> (50 modules) multi-module builds. So far, this has worked out OK. You
> can't sensibly maven release:perform from the root of such a project.
> When it's time to release you still have to do each sub-module
> separately. During development, however, it's a convenient way to
> check everything out and build everything together.
>
>
> Super simplified example:
>
> /repo/project-a/trunk (development, 1.1-SNAPSHOT)
> /repo/project-a/branches/1.0.x (a 1.0.x-SNAPSHOT release branch)
> /repo/project-a/tags/1.0.0
> /repo/project-b/trunk (development, 1.2-SNAPSHOT)
> /repo/project-b/branches/1.1.x (a 1.1.x-SNAPSHOT release branch)
> /repo/project-b/tags/1.1.0
>
> /repo/combined-release/trunk
> contains a pom.xml naming the submodules and defines svn:externals for
> /repo/project-a/trunk
> /repo/project-b/trunk
>
> /repo/combined-release/branches/1.0.x
> contains a pom.xml naming the submodules and defines svn:externals for
> /repo/project-a/branches/1.0.x
> /repo/project-b/branches/1.1.x
>
> /repo/combined-release/tags/1.0.0
> contains a pom.xml naming the submodules and defines svn:externals for
> /repo/project-a/tags/1.0.0
> /repo/project-b/tags/1.1.0
>
> Making something like the above release tag means editing the
> svn:externals to point at the correct project tags. There's no way (I
> know of) of getting maven to do this, as it's pretty SVN specific.
>
> // ben
>
> --
Re: Maven and Subversion.
On Tue, Apr 19, 2011 at 20:38, wrote: > I am wondering if anyone has a good solution to the following issue. > > I have a multi module maven configuration ( a pom that runs multiple poms > underneath it.). I made it a multi module project because the sub projects > are very similar and it is convenient to run them all from one pom. However, > I need each of these sub projects to be versioned independently. In > subversion, you need to make trunk, tags, and branches folders for each > project to do this. This breaks the multi module directory structure for > Maven as it requires the pom to be in the top level folder for each of the > sub projects. > > Does anyone have a solution as to the best way to make this work, or am I > stuck with not using the multi module project in Maven? > > Thanks, > > Todd In our repository we have the policy that only modules that are always released together can live in the same trunk. As a result we don't have many multi-module builds. This isn't all rainbows and unicorns, as this means more individual trunks to tag, more versions to keep track of, more things to build and deploy etc. For such cases, we've used svn:externals to pull together a few large (50 modules) multi-module builds. So far, this has worked out OK. You can't sensibly maven release:perform from the root of such a project. When it's time to release you still have to do each sub-module separately. During development, however, it's a convenient way to check everything out and build everything together. Super simplified example: /repo/project-a/trunk (development, 1.1-SNAPSHOT) /repo/project-a/branches/1.0.x (a 1.0.x-SNAPSHOT release branch) /repo/project-a/tags/1.0.0 /repo/project-b/trunk (development, 1.2-SNAPSHOT) /repo/project-b/branches/1.1.x (a 1.1.x-SNAPSHOT release branch) /repo/project-b/tags/1.1.0 /repo/combined-release/trunk contains a pom.xml naming the submodules and defines svn:externals for /repo/project-a/trunk /repo/project-b/trunk /repo/combined-release/branches/1.0.x contains a pom.xml naming the submodules and defines svn:externals for /repo/project-a/branches/1.0.x /repo/project-b/branches/1.1.x /repo/combined-release/tags/1.0.0 contains a pom.xml naming the submodules and defines svn:externals for /repo/project-a/tags/1.0.0 /repo/project-b/tags/1.1.0 Making something like the above release tag means editing the svn:externals to point at the correct project tags. There's no way (I know of) of getting maven to do this, as it's pretty SVN specific. // ben - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven and Subversion.
On Tue, Apr 19, 2011 at 2:38 PM, wrote: > I have a multi module maven configuration ( a pom that runs multiple poms > underneath it.). I made it a multi module project because the sub projects > are very similar and it is convenient to run them all from one pom. However, > I need each of these sub projects to be versioned independently. In > subversion, you need to make trunk, tags, and branches folders for each > project to do this. This breaks the multi module directory structure for > Maven as it requires the pom to be in the top level folder for each of the > sub projects. > > Does anyone have a solution as to the best way to make this work, or am I > stuck with not using the multi module project in Maven? If the grouping is *solely* for convenience and you are never going to release from that top level pom, then you can use svn externals to pull it all together. You'll have a directory that contains the top level pom, and has the svn:externals properties set. When you check out the directory, you'll get all the subdirectories. Several open source projects I've worked on have used this, there might be a "trunks" or "all" directory that pulls in all the interesting bits. For CI or when you're ready to release, go back to the 'real' trunk and do it from there. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven and Subversion.
I am wondering if anyone has a good solution to the following issue. I have a multi module maven configuration ( a pom that runs multiple poms underneath it.). I made it a multi module project because the sub projects are very similar and it is convenient to run them all from one pom. However, I need each of these sub projects to be versioned independently. In subversion, you need to make trunk, tags, and branches folders for each project to do this. This breaks the multi module directory structure for Maven as it requires the pom to be in the top level folder for each of the sub projects. Does anyone have a solution as to the best way to make this work, or am I stuck with not using the multi module project in Maven? Thanks, Todd
Re: Release plugin tagging parent of trunk
Thanks for the replies Roland, it's much appreciated, Here's some excerpts from the logs: Here is a log with dryRun=false where you can see the copy command for the tag using the project root instead of trunk. Also you can see that unlike the other parts of the execution where the script starts by going to the /project/workspace directory the tag script starts by changing to the /project directory, the only reason this doesn't fail outright is that it's doing a copy instead of something that acts on the current working directory. [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /u/wc/hudson_work/jobs/project/workspace && svn --username user --password '*' --non-interactive commit --file /tmp/maven-scm-2019473207.commit --targets /tmp/maven-scm-8595138965749612920-targets [INFO] Working directory: /u/wc/hudson_work/jobs/project/workspace [INFO] Tagging release with the label project-1.5.0... [INFO] Executing: /bin/sh -c cd /u/wc/hudson_work/jobs/project && svn --username user --password '*' --non-interactive copy --file /tmp/maven-scm-1342382552.commit --revision 238615 https://subversion.mycompany.com/java/project https://subversion.mycompany.com/java/project/tags/project-1.5.0 [INFO] Working directory: /u/wc/hudson_work/jobs/project [INFO] Transforming 'Project - Flex'... [INFO] Transforming 'Project - Java'... [INFO] Transforming 'Project Proxy'... [INFO] Transforming 'Project Proxy/API WAR'... [INFO] Updating project-proxy to 1.6.0-SNAPSHOT [INFO] Transforming 'Project Publisher'... [INFO] Transforming 'Project Publisher War'... [INFO] Updating project-publisher to 1.6.0-SNAPSHOT [INFO] Transforming 'Project Tool WAR'... [INFO] Transforming 'Project EAR'... [INFO] Updating project-proxy-war to 1.6.0-SNAPSHOT [INFO] Updating project-tool-war to 1.6.0-SNAPSHOT [INFO] Updating project-publisher-war to 1.6.0-SNAPSHOT [INFO] Transforming 'Project Master POM'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /u/wc/hudson_work/jobs/project/workspace && svn --username user --password '*' --non-interactive commit --file /tmp/maven-scm-192511325.commit --targets /tmp/maven-scm-7940317626122164433-targets [INFO] Working directory: /u/wc/hudson_work/jobs/project/workspace [INFO] Release preparation complete. Here's a log segment where I did a dry run showing that it fully intends on tagging the project root instead of the trunk.: [INFO] Full run would be tagging remotely scm:svn: https://subversion.mycompany.com/java/project with label: 'project-master-1.2.0' Here's a log where I set remoteTagging to false and you can see that it is now hanging up on the fact that it changed directory to /project instead of all the way to the working directory (like all the other scripts do). In this case I added an additional directory to the workspace called toQA just to demonstrate that it seems to be a level issue rather than a hard coded path: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /u/wc/hudson_work/jobs/project/workspace/toQA && svn --username dynamo --password '*' --non-interactive commit --file /tmp/maven-scm-283313407.commit --targets /tmp/maven-scm-1186996888170714263-targets [INFO] Working directory: /u/wc/hudson_work/jobs/project/workspace/toQA [INFO] Tagging release with the label project-master-1.2.0... [INFO] Executing: /bin/sh -c cd /u/wc/hudson_work/jobs/project/workspace && svn --username user --password '*' --non-interactive copy --file /tmp/maven-scm-777821000.commit . https://subversion.mycompany.com/java/project/tags/project-master-1.2.0 [INFO] Working directory: /u/wc/hudson_work/jobs/project/workspace These examples are obviously from a hudson server, but I've run it locally and experienced the same thing. Thanks again to anyone who has read this, even if you can't help me ;) Brent Brent Smith BScCS Software Developer, theREDspace Halifax, Nova Scotia, Canada Phone: 902.444.3490x3869 brent.sm...@theredspace.com On Tue, Apr 19, 2011 at 2:52 PM, Asmann, Roland wrote: > That looks correct to me... > And thinking about it, tagBase can't be the reason for this, since the > tag is actually in the right place. > > I'm afraid I don't know what else it could be... Maybe you could run a > release with debug-output and read something out of that? If not, you > could post it so all of us can take a crack at it. > >
Re: Release plugin tagging parent of trunk
That looks correct to me... And thinking about it, tagBase can't be the reason for this, since the tag is actually in the right place. I'm afraid I don't know what else it could be... Maybe you could run a release with debug-output and read something out of that? If not, you could post it so all of us can take a crack at it. On 19.04.2011 19:45, Brent Smith wrote: > The scm node seems correct, both and are > pointing at the trunk: > scm:svn:https://subversion.mycompany.com/java/project/trunk > > > I was under the impression that tagBase didn't need to be set if you were > using a standard trunk/branches/tags layout and would affect where the tag > was placed, not where it was tagged from. If I'm mistaken in this please let > me know. > > I don't have anything special going on with the release plugin itself, I'm > using -DautoVersionSubmodules=true but that's about it. > > Thanks, > Brent > > >Are you sure that your and / are > >correctly set? > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin tagging parent of trunk
The scm node seems correct, both and are pointing at the trunk: scm:svn:https://subversion.mycompany.com/java/project/trunk I was under the impression that tagBase didn't need to be set if you were using a standard trunk/branches/tags layout and would affect where the tag was placed, not where it was tagged from. If I'm mistaken in this please let me know. I don't have anything special going on with the release plugin itself, I'm using -DautoVersionSubmodules=true but that's about it. Thanks, Brent >Are you sure that your and / are >correctly set?
Re: Is it possible to run a mojo when using an archetype to start a project ?
Would it be OK if it runs after the archetype has been created? Afaik you can't have it run automatically, but you could add the parameter 'goals' to the call 'archetype:generate' to run your mojo... http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#goals On 19.04.2011 18:20, Gayard, Leonel wrote: > Hi, > > The title of the message says it all. I'm currently trying to create an > archetype. > > I understand that archetypes allow to generate new files from templates, > using FreeMarker. But I'd like to be able to have some code, either in a > Mojo or some quick script, that runs when the archetype is used to start > a new project. Is this possible ? How to proceed ? > > I've also asked Stack Overflow, but no luck yet: > http://stackoverflow.com/questions/5707677/making-a-maven-archetype-how-to-run-a-mojo-on-a-projects-generation > > Leonel > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Is it possible to run a mojo when using an archetype to start a project ?
Hi, The title of the message says it all. I'm currently trying to create an archetype. I understand that archetypes allow to generate new files from templates, using FreeMarker. But I'd like to be able to have some code, either in a Mojo or some quick script, that runs when the archetype is used to start a new project. Is this possible ? How to proceed ? I've also asked Stack Overflow, but no luck yet: http://stackoverflow.com/questions/5707677/making-a-maven-archetype-how-to-run-a-mojo-on-a-projects-generation Leonel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin tagging parent of trunk
Are you sure that your and / are correctly set? On 19.04.2011 18:01, Brent Smith wrote: > Hello, > > I'm running into an issue when I do a release:prepare on a multi-module > project where the tagging phase is tagging the parent of the trunk. I found > a bug report about something similar here: > http://jira.codehaus.org/browse/MRELEASE-562 however the workaround given in > a related ticket which worked for some people (remoteTagging=false) doesn't > seem to be working for me. > > I'm using a standard SVN structure > --project > trunk > branches > tags > > When the tag is created however it creates it from the \project folder, so > it includes trunk as well as all branches and tags > --project > trunk > branches > tags > --myTag > trunk > branches > tags > > I tried using remoteTagging=false but in that case the tag fails because it > tries to use a directory that is the parent of my workspace. Only the tag > does this, the commit for updating the version info uses the proper > location and executes immediately before the tag request. It seems like just > the tag creation is adamant about being one level too deep. If anyone could > shed some light on why this might be happening, or knows of a way to > explicitly set which location to tag from I'd really appreciate it. I have > recently refactored the project, adding an additional parent pom, however > I've checked all the poms and the locations in them look proper. > > Thanks, > Brent > > > Brent Smith BScCS > Software Developer, theREDspace > Halifax, Nova Scotia, Canada > Phone: 902.444.3490x3869 > brent.sm...@theredspace.com > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release plugin tagging parent of trunk
Hello, I'm running into an issue when I do a release:prepare on a multi-module project where the tagging phase is tagging the parent of the trunk. I found a bug report about something similar here: http://jira.codehaus.org/browse/MRELEASE-562 however the workaround given in a related ticket which worked for some people (remoteTagging=false) doesn't seem to be working for me. I'm using a standard SVN structure --project trunk branches tags When the tag is created however it creates it from the \project folder, so it includes trunk as well as all branches and tags --project trunk branches tags --myTag trunk branches tags I tried using remoteTagging=false but in that case the tag fails because it tries to use a directory that is the parent of my workspace. Only the tag does this, the commit for updating the version info uses the proper location and executes immediately before the tag request. It seems like just the tag creation is adamant about being one level too deep. If anyone could shed some light on why this might be happening, or knows of a way to explicitly set which location to tag from I'd really appreciate it. I have recently refactored the project, adding an additional parent pom, however I've checked all the poms and the locations in them look proper. Thanks, Brent Brent Smith BScCS Software Developer, theREDspace Halifax, Nova Scotia, Canada Phone: 902.444.3490x3869 brent.sm...@theredspace.com
Re: mvn eclipse plugin for multimodule proyect
Can you post your configuration (if any) and the command you issue to run Maven? On 19.04.2011 17:44, Fernando Wermus wrote: > What it does not create are the files for each eclipse project. Thus I > cannot make the import. > > 2011/4/19 Asmann, Roland > > > Doesn't it create the files or are your projects not in Eclipse? > > > > You must import the projects yourself after the build, the plugin does > > *not* do this for you! > > > > > > On 19.04.2011 17:14, Fernando Wermus wrote: > > > Hi all, > > > I have a pom which is a multimodule proyect. I am using maven plugin > > > eclipse for generating all the eclipse's proyects. But for reason, it > > > doesn't create any. > > > > > > any help would be really appreciated > > > > > > > -- > > Roland Asmann > > Senior Software Engineer > > > > adesso Austria GmbH > > Floridotower 26. Stock T +43 1 2198790-27 > > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > > A-1210 Wien M +43 664 88657566 > > E roland.asm...@adesso.at > > W www.adesso.at > > > > - > > >>> business. people. technology. <<< > > - > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn eclipse plugin for multimodule proyect
What it does not create are the files for each eclipse project. Thus I cannot make the import. 2011/4/19 Asmann, Roland > Doesn't it create the files or are your projects not in Eclipse? > > You must import the projects yourself after the build, the plugin does > *not* do this for you! > > > On 19.04.2011 17:14, Fernando Wermus wrote: > > Hi all, > > I have a pom which is a multimodule proyect. I am using maven plugin > > eclipse for generating all the eclipse's proyects. But for reason, it > > doesn't create any. > > > > any help would be really appreciated > > > > -- > Roland Asmann > Senior Software Engineer > > adesso Austria GmbH > Floridotower 26. Stock T +43 1 2198790-27 > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > A-1210 Wien M +43 664 88657566 >E roland.asm...@adesso.at >W www.adesso.at > > - > >>> business. people. technology. <<< > - > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: mvn eclipse plugin for multimodule proyect
Doesn't it create the files or are your projects not in Eclipse? You must import the projects yourself after the build, the plugin does *not* do this for you! On 19.04.2011 17:14, Fernando Wermus wrote: > Hi all, > I have a pom which is a multimodule proyect. I am using maven plugin > eclipse for generating all the eclipse's proyects. But for reason, it > doesn't create any. > > any help would be really appreciated > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mvn eclipse plugin for multimodule proyect
Hi all, I have a pom which is a multimodule proyect. I am using maven plugin eclipse for generating all the eclipse's proyects. But for reason, it doesn't create any. any help would be really appreciated
Re: error while deploying a project
For the tracking purpose, it was the problem with cargo-maven2-plugin that
is used to run embedded jetty server. This userlist may not be the right one
to post a question. Hence, i am posting the question on
u...@cargo.codehaus.org instead. :)
On Tue, Apr 19, 2011 at 8:42 PM, Nilesh - MiKu wrote:
> i better start a new thread, as the subject is misleading..
>
>
> On Tue, Apr 19, 2011 at 7:14 PM, Nilesh - MiKu wrote:
>
>> oh the solution worked.. thanks a ton...
>>
>> but it resulted in another problem...
>>
>> a bit of background..
>>
>> i have a multi module project.. deployment of top parent module got
>> successful (packaging type - pom)
>>
>> but at second level it failed... it gives following error.
>>
>> Cannot create deployable. There's no registered deployable for the
>> parameters (container [id = [default]], deployable type [pom]). Valid types
>> for this deployable are:
>> - ear
>> - war
>> - file
>> - rar
>> - sar
>> - ejb
>>
>> the pom.xml has following entry..
>>
>>
>> pw
>> base-dependencies
>> 1.0-SNAPSHOT
>>
>> 4.0.0
>> base
>> pom
>>
>> Note : base-dependencies have packaging of type pom. and that worked as i
>> have mentioned before.
>>
>> Link http://web.archiveorange.com/archive/v/F1XzEyz3zueRymFcSHZl seems to
>> be too much to circumvent this small error.. Also, the user complains that
>> it did not work..
>>
>> any clue?
>>
>> On Tue, Apr 19, 2011 at 3:55 PM, Stuart McCulloch wrote:
>>
>>> On 19 Apr 2011, at 11:08, Nilesh - MiKu wrote:
>>>
>>> > i m using maven 2.0.9 and recently i have shifted my repository to
>>> sonatype
>>> > nexus 1.9.0.2 from archiva.
>>> >
>>> > I have migrated all the necessary artifcats to sonatype nexus as
>>> explained
>>> > in their docs and found no errors while rebuilding any indexes
>>> whatsoever in
>>> > the logs. The migration was successful. However, while deploying one of
>>> the
>>> > project, i get following error..
>>> >
>>> > [INFO] Scanning for projects...
>>> > [INFO]
>>> >
>>>
>>> > [INFO] Building Unnamed - pw:pw-base-dependencies:pom:1.0-SNAPSHOT
>>> > [INFO]task-segment: [deploy]
>>> > [INFO]
>>> >
>>>
>>> > [INFO] [jar:test-jar {execution: default}]
>>> > [WARNING] JAR will be empty - no content was marked for inclusion!
>>> > [INFO] [site:attach-descriptor]
>>> > [INFO] Preparing source:jar
>>> > [WARNING] Removing: jar from forked lifecycle, to prevent recursive
>>> > invocation.
>>> > [INFO] No goals needed for project - skipping
>>> > [INFO] [source:jar {execution: default}]
>>> > [INFO] [install:install]
>>> > [INFO] Installing /somepath/base/base-dependencies/pom.xml to
>>> >
>>> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT.pom
>>> > [INFO] Installing
>>> >
>>> /somepath/base/base-dependencies/target/WEB-INF/lib/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
>>> > to
>>> >
>>> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
>>> > [INFO] [deploy:deploy]
>>> > altDeploymentRepository = null
>>> > [INFO] Retrieving previous build number from snapshots
>>> > [INFO]
>>> >
>>>
>>> > [ERROR] BUILD ERROR
>>> > [INFO]
>>> >
>>>
>>> > [INFO] Error retrieving previous build number for artifact
>>> > 'pw:pw-base-dependencies:pom': Cannot read metadata from
>>> >
>>> '/somepath/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/maven-metadata-snapshots.xml':
>>> > expected START_TAG or END_TAG not TEXT (position: TEXT seen
>>> > ...tests>> >
>>> > [INFO]
>>> >
>>>
>>> > [INFO] For more information, run Maven with the -e switch
>>> > [INFO]
>>> >
>>>
>>> > [INFO] Total time: 7 seconds
>>> > [INFO] Finished at: Thu Apr 14 21:10:06 IST 2011
>>> > [INFO] Final Memory: 18M/122M
>>> > [INFO]
>>> >
>>>
>>> >
>>> >
>>> > The contents of the file being complained
>>> > (i.e. maven-metadata-snapshots.xml) has following contents..
>>> >
>>> >
>>> >
>>> >
>>> > pw
>>> > pw-base-dependencies
>>> > 1.0-SNAPSHOT
>>> >
>>> >
>>> > 20100617.105422
>>> > 11
>>> >
>>> >20110411220259
>>> >
>>> >
>>> >tests
>>> >jar
>>> >1.0-20100617.105422-11
>>> >20100617105422
>>> >
>>> >
>>> >pom
>>> >1.0-20100617.105422-11
>>> >20100617105422
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Googling did not give any hint on what is to be done. And i dont
>>> understand
Re: error while deploying a project
i better start a new thread, as the subject is misleading..
On Tue, Apr 19, 2011 at 7:14 PM, Nilesh - MiKu wrote:
> oh the solution worked.. thanks a ton...
>
> but it resulted in another problem...
>
> a bit of background..
>
> i have a multi module project.. deployment of top parent module got
> successful (packaging type - pom)
>
> but at second level it failed... it gives following error.
>
> Cannot create deployable. There's no registered deployable for the
> parameters (container [id = [default]], deployable type [pom]). Valid types
> for this deployable are:
> - ear
> - war
> - file
> - rar
> - sar
> - ejb
>
> the pom.xml has following entry..
>
>
> pw
> base-dependencies
> 1.0-SNAPSHOT
>
> 4.0.0
> base
> pom
>
> Note : base-dependencies have packaging of type pom. and that worked as i
> have mentioned before.
>
> Link http://web.archiveorange.com/archive/v/F1XzEyz3zueRymFcSHZl seems to
> be too much to circumvent this small error.. Also, the user complains that
> it did not work..
>
> any clue?
>
> On Tue, Apr 19, 2011 at 3:55 PM, Stuart McCulloch wrote:
>
>> On 19 Apr 2011, at 11:08, Nilesh - MiKu wrote:
>>
>> > i m using maven 2.0.9 and recently i have shifted my repository to
>> sonatype
>> > nexus 1.9.0.2 from archiva.
>> >
>> > I have migrated all the necessary artifcats to sonatype nexus as
>> explained
>> > in their docs and found no errors while rebuilding any indexes
>> whatsoever in
>> > the logs. The migration was successful. However, while deploying one of
>> the
>> > project, i get following error..
>> >
>> > [INFO] Scanning for projects...
>> > [INFO]
>> >
>> > [INFO] Building Unnamed - pw:pw-base-dependencies:pom:1.0-SNAPSHOT
>> > [INFO]task-segment: [deploy]
>> > [INFO]
>> >
>> > [INFO] [jar:test-jar {execution: default}]
>> > [WARNING] JAR will be empty - no content was marked for inclusion!
>> > [INFO] [site:attach-descriptor]
>> > [INFO] Preparing source:jar
>> > [WARNING] Removing: jar from forked lifecycle, to prevent recursive
>> > invocation.
>> > [INFO] No goals needed for project - skipping
>> > [INFO] [source:jar {execution: default}]
>> > [INFO] [install:install]
>> > [INFO] Installing /somepath/base/base-dependencies/pom.xml to
>> >
>> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT.pom
>> > [INFO] Installing
>> >
>> /somepath/base/base-dependencies/target/WEB-INF/lib/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
>> > to
>> >
>> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
>> > [INFO] [deploy:deploy]
>> > altDeploymentRepository = null
>> > [INFO] Retrieving previous build number from snapshots
>> > [INFO]
>> >
>> > [ERROR] BUILD ERROR
>> > [INFO]
>> >
>> > [INFO] Error retrieving previous build number for artifact
>> > 'pw:pw-base-dependencies:pom': Cannot read metadata from
>> >
>> '/somepath/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/maven-metadata-snapshots.xml':
>> > expected START_TAG or END_TAG not TEXT (position: TEXT seen
>> > ...tests> >
>> > [INFO]
>> >
>> > [INFO] For more information, run Maven with the -e switch
>> > [INFO]
>> >
>> > [INFO] Total time: 7 seconds
>> > [INFO] Finished at: Thu Apr 14 21:10:06 IST 2011
>> > [INFO] Final Memory: 18M/122M
>> > [INFO]
>> >
>> >
>> >
>> > The contents of the file being complained
>> > (i.e. maven-metadata-snapshots.xml) has following contents..
>> >
>> >
>> >
>> >
>> > pw
>> > pw-base-dependencies
>> > 1.0-SNAPSHOT
>> >
>> >
>> > 20100617.105422
>> > 11
>> >
>> >20110411220259
>> >
>> >
>> >tests
>> >jar
>> >1.0-20100617.105422-11
>> >20100617105422
>> >
>> >
>> >pom
>> >1.0-20100617.105422-11
>> >20100617105422
>> >
>> >
>> >
>> >
>> >
>> >
>> > Googling did not give any hint on what is to be done. And i dont
>> understand
>> > what is wrong with this situation.
>>
>> Nexus 1.9 is serving up the latest format of maven metadata (see
>> http://jira.codehaus.org/browse/MNG-4452 for some background)
>>
>> If you update to Maven 2.0.10 then it can handle the additional entries
>> and the problem should go away
>>
>> > Please help. Please revert if some more
>> > information is needed.
>> >
>> >
>> > --
>> > Best Regards,
>> > Nilesh Mevada
>>
>>
[ANN] cobertura-maven-plugin 2.5 released
Hi, The Mojo team is pleased to announce the release of the cobertura-maven-plugin version P2.5. This plugin provides maven integration for the cobertura open source code coverage tool. For more information, see http://mojo.codehaus.org/cobertura-maven-plugin/. To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo cobertura-maven-plugin 2.5 It may be of particular interest that this release includes support for aggregation. Release Notes http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11226&version=16413 Enjoy, The Mojo team. Benson Margulies - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using classifiers, missing artifact
On 18 April 2011 17:09, Claves do Amaral wrote: > I am not sure how does the repository works. I am not managing it and > the team who is managing it is not easily reachable, therefore, I > cannot ask for help. I think I have a possible key to the solution. Reading the maven book on the Sonatype web site, it looks that for SNAPSHOT versions, the SNAPSHOT token in the version must be expanded to (substituted with) a time stamp. This is used to return the latest snapshot when it's requested. It looks this mechanism actually works for POMs, but fails for JARs, that have a classifier appended after the version, in their name. So, it looks there is something wrong here. Why do Maven fails to expand the SNAPSHOT in case a classifier is used? Is this a wanted behaviour or a bug? Cheers, Claves - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: error while deploying a project
oh the solution worked.. thanks a ton...
but it resulted in another problem...
a bit of background..
i have a multi module project.. deployment of top parent module got
successful (packaging type - pom)
but at second level it failed... it gives following error.
Cannot create deployable. There's no registered deployable for the
parameters (container [id = [default]], deployable type [pom]). Valid types
for this deployable are:
- ear
- war
- file
- rar
- sar
- ejb
the pom.xml has following entry..
pw
base-dependencies
1.0-SNAPSHOT
4.0.0
base
pom
Note : base-dependencies have packaging of type pom. and that worked as i
have mentioned before.
Link http://web.archiveorange.com/archive/v/F1XzEyz3zueRymFcSHZl seems to be
too much to circumvent this small error.. Also, the user complains that it
did not work..
any clue?
On Tue, Apr 19, 2011 at 3:55 PM, Stuart McCulloch wrote:
> On 19 Apr 2011, at 11:08, Nilesh - MiKu wrote:
>
> > i m using maven 2.0.9 and recently i have shifted my repository to
> sonatype
> > nexus 1.9.0.2 from archiva.
> >
> > I have migrated all the necessary artifcats to sonatype nexus as
> explained
> > in their docs and found no errors while rebuilding any indexes whatsoever
> in
> > the logs. The migration was successful. However, while deploying one of
> the
> > project, i get following error..
> >
> > [INFO] Scanning for projects...
> > [INFO]
> >
> > [INFO] Building Unnamed - pw:pw-base-dependencies:pom:1.0-SNAPSHOT
> > [INFO]task-segment: [deploy]
> > [INFO]
> >
> > [INFO] [jar:test-jar {execution: default}]
> > [WARNING] JAR will be empty - no content was marked for inclusion!
> > [INFO] [site:attach-descriptor]
> > [INFO] Preparing source:jar
> > [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> > invocation.
> > [INFO] No goals needed for project - skipping
> > [INFO] [source:jar {execution: default}]
> > [INFO] [install:install]
> > [INFO] Installing /somepath/base/base-dependencies/pom.xml to
> >
> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT.pom
> > [INFO] Installing
> >
> /somepath/base/base-dependencies/target/WEB-INF/lib/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
> > to
> >
> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
> > [INFO] [deploy:deploy]
> > altDeploymentRepository = null
> > [INFO] Retrieving previous build number from snapshots
> > [INFO]
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> >
> > [INFO] Error retrieving previous build number for artifact
> > 'pw:pw-base-dependencies:pom': Cannot read metadata from
> >
> '/somepath/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/maven-metadata-snapshots.xml':
> > expected START_TAG or END_TAG not TEXT (position: TEXT seen
> > ...tests >
> > [INFO]
> >
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> >
> > [INFO] Total time: 7 seconds
> > [INFO] Finished at: Thu Apr 14 21:10:06 IST 2011
> > [INFO] Final Memory: 18M/122M
> > [INFO]
> >
> >
> >
> > The contents of the file being complained
> > (i.e. maven-metadata-snapshots.xml) has following contents..
> >
> >
> >
> >
> > pw
> > pw-base-dependencies
> > 1.0-SNAPSHOT
> >
> >
> > 20100617.105422
> > 11
> >
> >20110411220259
> >
> >
> >tests
> >jar
> >1.0-20100617.105422-11
> >20100617105422
> >
> >
> >pom
> >1.0-20100617.105422-11
> >20100617105422
> >
> >
> >
> >
> >
> >
> > Googling did not give any hint on what is to be done. And i dont
> understand
> > what is wrong with this situation.
>
> Nexus 1.9 is serving up the latest format of maven metadata (see
> http://jira.codehaus.org/browse/MNG-4452 for some background)
>
> If you update to Maven 2.0.10 then it can handle the additional entries and
> the problem should go away
>
> > Please help. Please revert if some more
> > information is needed.
> >
> >
> > --
> > Best Regards,
> > Nilesh Mevada
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Best Regards,
Nilesh Mevada
Re: Ho do I include test jars in an assembly?
On Tue, Apr 19, 2011 at 9:24 PM, Rupert Smith wrote: > I should also add. There seem to be 3 issues here: > > * Adding a :test classifier to a module set include, should include the test > jar. > * The syntax of the artifact vector needs to be clarified in documentation, > wrt how wild cards are used. That is, is it group:artifact:*:*:test or > group:artifact:*:test or ... > * When specifying a test classifier is it 'test' or 'tests'? The scope seems > to be called 'test' and the classifier seems to be 'tests', this is very > confusing. I think you should be using "type" = "test-jar". http://maven.apache.org/plugins/maven-assembly-plugin/advanced-descriptor-topics.html (See http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_dependency http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html is what generates the test-jar) So I suspect that using the pattern groupId:artifactId:type:classifier com.rapidaddition:genzero-runtests:test-jar would work (where here classifier is null) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to model dependency from Unit Test Source to a another Projects Source
It was really no problem with the dependency I didn't had any dependency to another project, it was really a java compilation problem itself. So I don't have any real solution for the problem I had posted. -Ursprüngliche Nachricht- Von: Barrie Treloar [mailto:baerr...@gmail.com] Gesendet: Dienstag, 19. April 2011 14:33 An: Maven Users List Betreff: Re: How to model dependency from Unit Test Source to a another Projects Source On Tue, Apr 19, 2011 at 4:40 PM, Sailer, Richard wrote: > Hello all, > > I solved the problem it was not a dependency it was compilation problem. > So thanks for your help. > > Richard You sure? Can you post how you solved it for the archives? Unit test code is not included in your normal artifacts, since only src/main/java and src/main/resources get processed into that. src/test/java and src/test/resources will get bundled into a test-jar when you included http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html as an execution for the jar plugin. You then need to make sure that the other project specifies it as a dependency (See http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_dependency) You need to set the dependency "type" to "test-jar". - 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: How to model dependency from Unit Test Source to a another Projects Source
On Tue, Apr 19, 2011 at 4:40 PM, Sailer, Richard wrote: > Hello all, > > I solved the problem it was not a dependency it was compilation problem. > So thanks for your help. > > Richard You sure? Can you post how you solved it for the archives? Unit test code is not included in your normal artifacts, since only src/main/java and src/main/resources get processed into that. src/test/java and src/test/resources will get bundled into a test-jar when you included http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html as an execution for the jar plugin. You then need to make sure that the other project specifies it as a dependency (See http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_dependency) You need to set the dependency "type" to "test-jar". - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven+clearcase integration
I am planning to integrate Clearcase UCM(under dynamic view) with Maven. 1) I found that Maven SCM is partially implemented for clearcase. Is there are any still issue with this? what is meaning partailly implemented SCM? 2) How compatable Clearcase with Maven? 3)Any issues or limitation with this 2 tools integration? 4)Maven docs says that it is not possible to use SCM plugin features like creating tags (applying labels), creating Change logs, and so on. 5) where can i find good document to integrate Maven with clearcase?. Apache site have given, but it is not very clear for beginners.
Re: Ho do I include test jars in an assembly?
I should also add. There seem to be 3 issues here:
* Adding a :test classifier to a module set include, should include the test
jar.
* The syntax of the artifact vector needs to be clarified in documentation,
wrt how wild cards are used. That is, is it group:artifact:*:*:test or
group:artifact:*:test or ...
* When specifying a test classifier is it 'test' or 'tests'? The scope seems
to be called 'test' and the classifier seems to be 'tests', this is very
confusing.
Are there JIRAs for the above/should I create them?
Rupert
On 19 April 2011 12:40, Rupert Smith wrote:
> Ok this worked:
>
>
>
>
>
> genzero-runtests/target/genzero-runtests-${genzero.version}-tests.jar
> lib
> false
> 0644
>
>
>
> And in the top-level POM:
>
>
> 1.2-RC4-SNAPSHOT
>
> (I have a bash script that uses sed on the POM files to bump the version).
>
> Is it better practice to define the assembly plugin in the top-level POM or
> in a seperate module? e.g.
>
> /pom.xml <- here
> module1/pom.xml (code + tests)
> build-module/pom.xml <--- or here?
>
> The reason I ask is that it occurs to be that the top-level pom cannot have
> module1 as a dependency (cyclic), but build-module could. Therefore, from
> build-module module1 and module1:test might both be visible as dependencies
> of the assembly.
>
> If anyone know a less cludgy way to include my tests, please enlighten me.
> For now, I need to get on with setting up some testing...
>
> Rupert
>
> On 19 April 2011 12:29, Rupert Smith wrote:
>
>> Logically, that would seem to be the wrong place to specify the scope; It
>> isn't that junit-toolkit as a dependency is not being found, its
>> genzero-runtime-VERSION-tests.jar which is the parent of that dependency
>> which is not even being picked up. However, I tried your suggestion out:
>>
>>
>>
>>
>>
>> com.rapidaddition:genzero-runtests:jar:1.2-RC4-SNAPSHOT:tests
>>
>>
>> lib
>> false
>> 0644
>> 0755
>>
>>
>>
>> com.thesett:junit-toolkit
>>
>> tests
>>
>>
>>
>>
>>
>> I tried a scope value of 'test' and 'tests', but neither work.
>>
>> I also tried putting the genzero-runtests dependency, not in a module set
>> (after all its not a module but an additional jar arising as a side effect
>> of building a module), but in a dependencySet at the top level of the
>> assembly XML. This did not work either (tried scope test/tests there too), I
>> guess because it is not a dependency of the top-level POM where the assembly
>> plugin is defined.
>>
>> Maybe a fileSet with a hard coded path to the target directory where the
>> .jar can be found at the end of the build? I can put the version in a
>> variable and hope that variable expansion works in the path definition,
>> e.g.,
>> genzero-runtest/target/genzero-runtests-${project.version}-test.jar.
>> Cludgy, but do I feel lucky?
>>
>> Rupert
>>
>> On 19 April 2011 12:14, Eike Kettner wrote:
>>
>>> Hi
>>>
>>> did you try to add test scope using the tag inside the
>>> tag? It's default value is "runtime"...
>>>
>>> found here
>>>
>>> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
>>>
>>>
>>> regards,
>>> Eike
>>>
>>>
>>> On [Tue, 19.04.2011 12:07], Rupert Smith wrote:
>>> > This question has come up a few times, but I see no definite answer in
>>> the
>>> > replies. If someone known how to do this, please let me know, I am
>>> tearing
>>> > my hair out and its no fun running the build over and over again an
>>> looking
>>> > at the output to see if it worked
>>> >
>>> > This is the relevant section of my assembly.xml:
>>> >
>>> >
>>> >
>>> >
>>> com.rapidaddition:genzero-runtests:*:test
>>> >
>>> >
>>> > lib
>>> > false
>>> > 0644
>>> > 0755
>>> >
>>> >
>>> >
>>> >
>>> com.thesett:junit-toolkit
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > For the module include I have also tried:
>>> >
>>> > com.rapidaddition:genzero-runtests:*:*:test
>>> > com.rapidaddition:genzero-runtests:*:tests
>>> > com.rapidaddition:genzero-runtests:*:*:tests
>>> >
>>> > But none seems to be right. Perhaps I should try filling in the type
>>> and
>>> > version too?
>>> >
>>> > Is including a test jar actually possible?
>>> >
>>> > To head of the inevitable question, why would I want to do such a
>>> thing... I
>>> > could put the tests in a separate module and include as an ordinary jar
>>> with
>>> > no 'test' classifier, but
Re: Ho do I include test jars in an assembly?
Ok this worked:
genzero-runtests/target/genzero-runtests-${genzero.version}-tests.jar
lib
false
0644
And in the top-level POM:
1.2-RC4-SNAPSHOT
(I have a bash script that uses sed on the POM files to bump the version).
Is it better practice to define the assembly plugin in the top-level POM or
in a seperate module? e.g.
/pom.xml <- here
module1/pom.xml (code + tests)
build-module/pom.xml <--- or here?
The reason I ask is that it occurs to be that the top-level pom cannot have
module1 as a dependency (cyclic), but build-module could. Therefore, from
build-module module1 and module1:test might both be visible as dependencies
of the assembly.
If anyone know a less cludgy way to include my tests, please enlighten me.
For now, I need to get on with setting up some testing...
Rupert
On 19 April 2011 12:29, Rupert Smith wrote:
> Logically, that would seem to be the wrong place to specify the scope; It
> isn't that junit-toolkit as a dependency is not being found, its
> genzero-runtime-VERSION-tests.jar which is the parent of that dependency
> which is not even being picked up. However, I tried your suggestion out:
>
>
>
>
>
> com.rapidaddition:genzero-runtests:jar:1.2-RC4-SNAPSHOT:tests
>
>
> lib
> false
> 0644
> 0755
>
>
>
> com.thesett:junit-toolkit
>
> tests
>
>
>
>
>
> I tried a scope value of 'test' and 'tests', but neither work.
>
> I also tried putting the genzero-runtests dependency, not in a module set
> (after all its not a module but an additional jar arising as a side effect
> of building a module), but in a dependencySet at the top level of the
> assembly XML. This did not work either (tried scope test/tests there too), I
> guess because it is not a dependency of the top-level POM where the assembly
> plugin is defined.
>
> Maybe a fileSet with a hard coded path to the target directory where the
> .jar can be found at the end of the build? I can put the version in a
> variable and hope that variable expansion works in the path definition,
> e.g.,
> genzero-runtest/target/genzero-runtests-${project.version}-test.jar.
> Cludgy, but do I feel lucky?
>
> Rupert
>
> On 19 April 2011 12:14, Eike Kettner wrote:
>
>> Hi
>>
>> did you try to add test scope using the tag inside the
>> tag? It's default value is "runtime"...
>>
>> found here
>>
>> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
>>
>>
>> regards,
>> Eike
>>
>>
>> On [Tue, 19.04.2011 12:07], Rupert Smith wrote:
>> > This question has come up a few times, but I see no definite answer in
>> the
>> > replies. If someone known how to do this, please let me know, I am
>> tearing
>> > my hair out and its no fun running the build over and over again an
>> looking
>> > at the output to see if it worked
>> >
>> > This is the relevant section of my assembly.xml:
>> >
>> >
>> >
>> >
>> com.rapidaddition:genzero-runtests:*:test
>> >
>> >
>> > lib
>> > false
>> > 0644
>> > 0755
>> >
>> >
>> >
>> > com.thesett:junit-toolkit
>> >
>> >
>> >
>> >
>> >
>> >
>> > For the module include I have also tried:
>> >
>> > com.rapidaddition:genzero-runtests:*:*:test
>> > com.rapidaddition:genzero-runtests:*:tests
>> > com.rapidaddition:genzero-runtests:*:*:tests
>> >
>> > But none seems to be right. Perhaps I should try filling in the type and
>> > version too?
>> >
>> > Is including a test jar actually possible?
>> >
>> > To head of the inevitable question, why would I want to do such a
>> thing... I
>> > could put the tests in a separate module and include as an ordinary jar
>> with
>> > no 'test' classifier, but I want these to be unit tests that run on
>> > every build AND I want to put them in an assembly to create a
>> distribution
>> > that I can give to customers who want a copy of the tests to run on
>> their
>> > own hardware too.
>> >
>> > Many thanks for any assistance.
>> >
>> > Rupert
>>
>> --
>> email: e...@eknet.org https://www.eknet.org pgp: 481161A0
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
Re: Ho do I include test jars in an assembly?
Logically, that would seem to be the wrong place to specify the scope; It
isn't that junit-toolkit as a dependency is not being found, its
genzero-runtime-VERSION-tests.jar which is the parent of that dependency
which is not even being picked up. However, I tried your suggestion out:
com.rapidaddition:genzero-runtests:jar:1.2-RC4-SNAPSHOT:tests
lib
false
0644
0755
com.thesett:junit-toolkit
tests
I tried a scope value of 'test' and 'tests', but neither work.
I also tried putting the genzero-runtests dependency, not in a module set
(after all its not a module but an additional jar arising as a side effect
of building a module), but in a dependencySet at the top level of the
assembly XML. This did not work either (tried scope test/tests there too), I
guess because it is not a dependency of the top-level POM where the assembly
plugin is defined.
Maybe a fileSet with a hard coded path to the target directory where the
.jar can be found at the end of the build? I can put the version in a
variable and hope that variable expansion works in the path definition,
e.g.,
genzero-runtest/target/genzero-runtests-${project.version}-test.jar.
Cludgy, but do I feel lucky?
Rupert
On 19 April 2011 12:14, Eike Kettner wrote:
> Hi
>
> did you try to add test scope using the tag inside the
> tag? It's default value is "runtime"...
>
> found here
>
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
>
>
> regards,
> Eike
>
>
> On [Tue, 19.04.2011 12:07], Rupert Smith wrote:
> > This question has come up a few times, but I see no definite answer in
> the
> > replies. If someone known how to do this, please let me know, I am
> tearing
> > my hair out and its no fun running the build over and over again an
> looking
> > at the output to see if it worked
> >
> > This is the relevant section of my assembly.xml:
> >
> >
> >
> >
> com.rapidaddition:genzero-runtests:*:test
> >
> >
> > lib
> > false
> > 0644
> > 0755
> >
> >
> >
> > com.thesett:junit-toolkit
> >
> >
> >
> >
> >
> >
> > For the module include I have also tried:
> >
> > com.rapidaddition:genzero-runtests:*:*:test
> > com.rapidaddition:genzero-runtests:*:tests
> > com.rapidaddition:genzero-runtests:*:*:tests
> >
> > But none seems to be right. Perhaps I should try filling in the type and
> > version too?
> >
> > Is including a test jar actually possible?
> >
> > To head of the inevitable question, why would I want to do such a
> thing... I
> > could put the tests in a separate module and include as an ordinary jar
> with
> > no 'test' classifier, but I want these to be unit tests that run on
> > every build AND I want to put them in an assembly to create a
> distribution
> > that I can give to customers who want a copy of the tests to run on their
> > own hardware too.
> >
> > Many thanks for any assistance.
> >
> > Rupert
>
> --
> email: e...@eknet.org https://www.eknet.org pgp: 481161A0
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Ho do I include test jars in an assembly?
Hi did you try to add test scope using the tag inside the tag? It's default value is "runtime"... found here http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet regards, Eike On [Tue, 19.04.2011 12:07], Rupert Smith wrote: > This question has come up a few times, but I see no definite answer in the > replies. If someone known how to do this, please let me know, I am tearing > my hair out and its no fun running the build over and over again an looking > at the output to see if it worked > > This is the relevant section of my assembly.xml: > > > > com.rapidaddition:genzero-runtests:*:test > > > lib > false > 0644 > 0755 > > > > com.thesett:junit-toolkit > > > > > > > For the module include I have also tried: > > com.rapidaddition:genzero-runtests:*:*:test > com.rapidaddition:genzero-runtests:*:tests > com.rapidaddition:genzero-runtests:*:*:tests > > But none seems to be right. Perhaps I should try filling in the type and > version too? > > Is including a test jar actually possible? > > To head of the inevitable question, why would I want to do such a thing... I > could put the tests in a separate module and include as an ordinary jar with > no 'test' classifier, but I want these to be unit tests that run on > every build AND I want to put them in an assembly to create a distribution > that I can give to customers who want a copy of the tests to run on their > own hardware too. > > Many thanks for any assistance. > > Rupert -- email: e...@eknet.org https://www.eknet.org pgp: 481161A0 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Ho do I include test jars in an assembly?
This question has come up a few times, but I see no definite answer in the replies. If someone known how to do this, please let me know, I am tearing my hair out and its no fun running the build over and over again an looking at the output to see if it worked This is the relevant section of my assembly.xml: com.rapidaddition:genzero-runtests:*:test lib false 0644 0755 com.thesett:junit-toolkit For the module include I have also tried: com.rapidaddition:genzero-runtests:*:*:test com.rapidaddition:genzero-runtests:*:tests com.rapidaddition:genzero-runtests:*:*:tests But none seems to be right. Perhaps I should try filling in the type and version too? Is including a test jar actually possible? To head of the inevitable question, why would I want to do such a thing... I could put the tests in a separate module and include as an ordinary jar with no 'test' classifier, but I want these to be unit tests that run on every build AND I want to put them in an assembly to create a distribution that I can give to customers who want a copy of the tests to run on their own hardware too. Many thanks for any assistance. Rupert
Re: Using Maven in Desktop Application
On Tue, Apr 19, 2011 at 12:34, Alok wrote: > Hi , > > I am developing an Desktop Application. I would like to use Maven as build > tool . Please let me know , can i use maven in desktop application? Maven is a build tool, it can build any Java project. It can build a lot of other things as well, you need to specify more details if this answer doesn't address your question. HTH Thomas > > Thanks in advance, > Regards, > Alok > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Using-Maven-in-Desktop-Application-tp4312961p4312961.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 > > -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg Better software through faster feedback - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using Maven in Desktop Application
Hi , I am developing an Desktop Application. I would like to use Maven as build tool . Please let me know , can i use maven in desktop application? Thanks in advance, Regards, Alok -- View this message in context: http://maven.40175.n5.nabble.com/Using-Maven-in-Desktop-Application-tp4312961p4312961.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: error while deploying a project
On 19 Apr 2011, at 11:08, Nilesh - MiKu wrote:
> i m using maven 2.0.9 and recently i have shifted my repository to sonatype
> nexus 1.9.0.2 from archiva.
>
> I have migrated all the necessary artifcats to sonatype nexus as explained
> in their docs and found no errors while rebuilding any indexes whatsoever in
> the logs. The migration was successful. However, while deploying one of the
> project, i get following error..
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - pw:pw-base-dependencies:pom:1.0-SNAPSHOT
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [jar:test-jar {execution: default}]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] [site:attach-descriptor]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: default}]
> [INFO] [install:install]
> [INFO] Installing /somepath/base/base-dependencies/pom.xml to
> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT.pom
> [INFO] Installing
> /somepath/base/base-dependencies/target/WEB-INF/lib/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
> to
> /home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from snapshots
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error retrieving previous build number for artifact
> 'pw:pw-base-dependencies:pom': Cannot read metadata from
> '/somepath/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/maven-metadata-snapshots.xml':
> expected START_TAG or END_TAG not TEXT (position: TEXT seen
> ...tests
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Apr 14 21:10:06 IST 2011
> [INFO] Final Memory: 18M/122M
> [INFO]
>
>
>
> The contents of the file being complained
> (i.e. maven-metadata-snapshots.xml) has following contents..
>
>
>
>
> pw
> pw-base-dependencies
> 1.0-SNAPSHOT
>
>
> 20100617.105422
> 11
>
>20110411220259
>
>
>tests
>jar
>1.0-20100617.105422-11
>20100617105422
>
>
>pom
>1.0-20100617.105422-11
>20100617105422
>
>
>
>
>
>
> Googling did not give any hint on what is to be done. And i dont understand
> what is wrong with this situation.
Nexus 1.9 is serving up the latest format of maven metadata (see
http://jira.codehaus.org/browse/MNG-4452 for some background)
If you update to Maven 2.0.10 then it can handle the additional entries and the
problem should go away
> Please help. Please revert if some more
> information is needed.
>
>
> --
> Best Regards,
> Nilesh Mevada
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
error while deploying a project
i m using maven 2.0.9 and recently i have shifted my repository to sonatype
nexus 1.9.0.2 from archiva.
I have migrated all the necessary artifcats to sonatype nexus as explained
in their docs and found no errors while rebuilding any indexes whatsoever in
the logs. The migration was successful. However, while deploying one of the
project, i get following error..
[INFO] Scanning for projects...
[INFO]
[INFO] Building Unnamed - pw:pw-base-dependencies:pom:1.0-SNAPSHOT
[INFO]task-segment: [deploy]
[INFO]
[INFO] [jar:test-jar {execution: default}]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: default}]
[INFO] [install:install]
[INFO] Installing /somepath/base/base-dependencies/pom.xml to
/home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT.pom
[INFO] Installing
/somepath/base/base-dependencies/target/WEB-INF/lib/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
to
/home/nilesh/MiKuStuff/Workspace/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/pw-base-dependencies-1.0-SNAPSHOT-tests.jar
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from snapshots
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error retrieving previous build number for artifact
'pw:pw-base-dependencies:pom': Cannot read metadata from
'/somepath/_app_base/Maven2Repo/pw/pw-base-dependencies/1.0-SNAPSHOT/maven-metadata-snapshots.xml':
expected START_TAG or END_TAG not TEXT (position: TEXT seen
...tests
pw
pw-base-dependencies
1.0-SNAPSHOT
20100617.105422
11
20110411220259
tests
jar
1.0-20100617.105422-11
20100617105422
pom
1.0-20100617.105422-11
20100617105422
Googling did not give any hint on what is to be done. And i dont understand
what is wrong with this situation. Please help. Please revert if some more
information is needed.
--
Best Regards,
Nilesh Mevada
Re: how to read plugin.xml using Maven API
Check how the maven-plugin-plugin reads this info. /Anders On Tue, Apr 19, 2011 at 10:28, amaresh mourya wrote: > Hi All, > > Is there any maven API that can provide me the list of goals from a plugin > or no of parameters of a goal and other information. I can see these > information written in META_INF/maven/plugin.xml of plugin's JAR. Is there > some API to read it and return me the required information. > > Thanks > Amaresh >
how to read plugin.xml using Maven API
Hi All, Is there any maven API that can provide me the list of goals from a plugin or no of parameters of a goal and other information. I can see these information written in META_INF/maven/plugin.xml of plugin's JAR. Is there some API to read it and return me the required information. Thanks Amaresh
AW: How to model dependency from Unit Test Source to a another Projects Source
Hello all, I solved the problem it was not a dependency it was compilation problem. So thanks for your help. Richard -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 18. April 2011 11:21 An: Maven Users List Betreff: Re: How to model dependency from Unit Test Source to a another Projects Source OK, then I guess it must be either the coordinates that are incorrect or the scope set to runtime. The runtime scope sounds unlikely to me. /Anders On Mon, Apr 18, 2011 at 11:13, Sailer, Richard wrote: > Thanks for your reply. > > The project a is already a maven project and is installed in the mvn repo > correctly because all the other sources from project b compiles correctly. > Therefore it seems really strange to me. > > Richard > > -Ursprüngliche Nachricht- > Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im > Auftrag von Anders Hammar > Gesendet: Montag, 18. April 2011 10:34 > An: Maven Users List > Betreff: Re: How to model dependency from Unit Test Source to a another > Projects Source > > It should work as it is I believe (if the coordinates of project a are > correct). Possible you just need to build the a project so that it is > copied > to the local repo by > mvn install > > /Anders > > On Mon, Apr 18, 2011 at 09:02, Sailer, Richard < > richard.sai...@cassidian.com > > wrote: > > > Hello, > > > > I try to execute our unit tests with maven. The problem that I know get > > is a compilation failure (Cannot find class), when maven tries to > > compile the Unit Test souces in these sources we import a Class from > > another sub projects normal src Directory. > > > > So what I have is the following situation: > > > > Subproject project_a: > > I have Class name a1.java on the file System it looks like > > a/src/a1.java > > > > In Subproject project_b: > > I have another Classes and the Unit Tests: > > b/src/b1.java > > and also > > b/test/src.c1 > > In the class c1 I have a import to a1.java. > > When the test sources being compiled I get the compilation failure in > > Class c1 cannot filnd symbol a1. > > > > The dependency in the pom file in project b is modeled like this: > > > > > > > > com.xxx > > a > > > > > > > > > > > > So my question Is how do I have to model theses dependency in the pom. > > file so that the class a1 can be found ?? > > Must model the dependency additionaly in another Scope ? > > > > Thanks for your help. > > I really try to solve this problem since a while and I'm quite new to > > maven. > > > > Regards > > Richard Sailer > > > > - > 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
