Re: Creating a maven variable
Thanks martin, problem got resolved (still to figure out why wasn't it
working earlier). I am using a property now, which seems to work, now the
issue lies with buildnumber-maven-plugin , i am not able to have two
separate buildNumbers with different formats.
Thanks adn regards,
Amit
On Tue, Apr 29, 2008 at 12:13 PM, Martin Höller <[EMAIL PROTECTED]> wrote:
> On Monday 28 April 2008 amit kumar wrote:
> > Hi Olivier,
> > I tried the same thing in the root pom. But at the sub module level it
> > was taking ${my.build.directory} as {basedir}/${my.build.directory}, so
> > the error that was coming was like could not create *
> > D:\myProjects\project1\C:\builds\my-artifact-1.0.jar*
>
> The contents of the variable ${my.build.directory} is probably correct
> (verify it by using an antrun echo task). I bet the problem is the plugin
> using your variable. This plugin might not accept absolute path but only
> relative ones (like most maven-plugins do).
>
> See also this thread and the provided link to Brian's blog:
>
> http://www.nabble.com/Using-a-distribution-built-by-the-assembly-plugin-as-a-dependency...-to16887959s177.html
>
> hth,
> - martin
>
Re: how to use buildnumber-maven-plugin
I am inheriting the ${build.directory} property from the root project and
then in children projects i am trying to give the as -
${buildNumber} but its taking the format same as I defined in the root pom.
Any ideas?
Amit
On Tue, Apr 29, 2008 at 2:50 PM, amit kumar <[EMAIL PROTECTED]>
wrote:
> Can I have two separate variables containing build number values in
> different format?
> Actually want to use build number for both the build directory name and
> the time stamp in jar file names.
> so a buildnumber with format MM-DD- be the build directory name
> and MM-DD--HH-mm gets appended to the jar names and in the manifest
> file.
>
>
> Regards,
> Amit
>
>
> On Tue, Mar 11, 2008 at 7:09 PM, Rex Huang <[EMAIL PROTECTED]> wrote:
>
> > Thank you for your suggestion,
> > but it seems not working correcttly for the bug of this plugin.
> >
> > the results as below:
> > [buildnumber:create {execution: generate-buildnumber}]
> > Storing buildNumber: 16 at timestamp: 1205242293453
> > [buildnumber:create {execution: generate-timestamp}]
> > Storing buildNumber: Tue Mar 11 14:31 CET 2008 at timestamp:
> > 1205242293453
> >
>
>
Re: how to use buildnumber-maven-plugin
Can I have two separate variables containing build number values in
different format?
Actually want to use build number for both the build directory name and the
time stamp in jar file names.
so a buildnumber with format MM-DD- be the build directory name
and MM-DD--HH-mm gets appended to the jar names and in the manifest
file.
Regards,
Amit
On Tue, Mar 11, 2008 at 7:09 PM, Rex Huang <[EMAIL PROTECTED]> wrote:
> Thank you for your suggestion,
> but it seems not working correcttly for the bug of this plugin.
>
> the results as below:
> [buildnumber:create {execution: generate-buildnumber}]
> Storing buildNumber: 16 at timestamp: 1205242293453
> [buildnumber:create {execution: generate-timestamp}]
> Storing buildNumber: Tue Mar 11 14:31 CET 2008 at timestamp: 1205242293453
>
Re: Creating a maven variable
Hi Olivier,
I tried the same thing in the root pom. But at the sub module level it was
taking ${my.build.directory} as {basedir}/${my.build.directory}, so the
error that was coming was like could not create *
D:\myProjects\project1\C:\builds\my-artifact-1.0.jar*
Is the any work around to this?
Regards,
Amit
On Mon, Apr 28, 2008 at 5:35 PM, Olivier Dehon <[EMAIL PROTECTED]> wrote:
> Avoid redefining variables that are (or might be) defined by maven
> itself.
>
> Use something like:
>
>
>C:/builds
>
>
> instead.
>
> HTH, -Olivier
>
> On Mon, 2008-04-28 at 16:13 +0530, amit kumar wrote:
> > Hi,
> > I want to create a variable that can take a value of directory path on
> the
> > system and that variable can be read by children projects of the
> project. I
> > tried with
> >
> > C:\builds
> >
> >
> > but problem with this is that ${build.directory} seems to be taken as
> > ${basedir}/${build.directory} which ultimately throws an error since the
> > C:\builds is not in the ${basedir}. Any clues?
> >
> > The reason for having having the value in the variable is because I am
> > trying to put all the builds of a project in a dynamic folder named with
> > that particular day's date.
> >
> >
> > Regards,
> > Amit
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Creating a maven variable
Hi,
I want to create a variable that can take a value of directory path on the
system and that variable can be read by children projects of the project. I
tried with
C:\builds
but problem with this is that ${build.directory} seems to be taken as
${basedir}/${build.directory} which ultimately throws an error since the
C:\builds is not in the ${basedir}. Any clues?
The reason for having having the value in the variable is because I am
trying to put all the builds of a project in a dynamic folder named with
that particular day's date.
Regards,
Amit
Re: Customizing Build order
Yes. But even from parent pom, only mvn install or higher works, anything lower than install results in an error if the dependency project not in local repository otherwise if there takes an older version existing in local repository or remote. Regards, Amit On Fri, Mar 21, 2008 at 7:56 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > What you are asking for doesn't exist, but is covered by some proposals: > > http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode > http://jira.codehaus.org/browse/MNG-2576 > http://jira.codehaus.org/browse/MNG-1694 > > The reordering only happens when you build from a parent pom that > aggregates all your children. Otherwise, currently, you need to have the > dependencies installed in your repository. > > --Brian > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2008 9:32 AM > To: Maven Users List > Subject: Re: Customizing Build order > > How to list that dependency? I do have the dependency of A3 on B1 and > B2(in > the tag as jar). But that doesn't seems to make Maven go to > build B1 and B2 when building A3 because I guess it looks in the > repository, > if not there it throws an error. > > If it has been working in this way, it would have been the solution. But > I > am not able to see that happening. > > Is there a different way of mentioning a project As' dependency on > another > projectB that would trigger the build of projectB as soon as it finds in > the > dependencies? of that project? > > > Regards, > Amit. > > On Wed, Mar 19, 2008 at 6:49 AM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > > > Maven starts with the ordering listed in the poms (A and its children, > > then B and its children, etc) unless there is a dependency. If it sees > a > > dependency, then it will automatically reorder by pushing down modules > > that have a dependency so they build after their dep. > > > > I'm wondering why the order matters if you don't have a dependency > > listed (I'm assuming you don't or it would be ordered already). > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 18, 2008 4:42 AM > > To: Maven Users List > > Subject: Customizing Build order > > > > Hi, > > I have a multi-module project with the following structure. > > > > Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > In the Root's pom i have mentioned my modules as: > > A > > B > > > > Now is there a way that I can change the normal build order(which is) > > > > -Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > to something like > > > > -Root > > -A > > -A1 > > -A2 > > -B > > -B1 > > -B2 > > -A3 > > -B4 > > > > It is actually a requirement. But I doubt that there is a possibility > > that > > the CVS structure itself is not competent enough then to handle > > inter-module > > dependencies. > > > > Any inputs? > > > > Thanks and regards, > > Amit Kumar > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: pde-maven-plugin calls wrong ant target
Thanks Jeroen. That would be a great help. Although I am not hands on with svn and don't know how to checkout a particular version from it. But definitely would give it a shot. I am using eclipse 3.3 and maven 2.0.7 Thanks and regards, Amit On Wed, Mar 19, 2008 at 12:37 PM, Jeroen Lankheet <[EMAIL PROTECTED]> wrote: > > The last remark I made can safely be ignored. > I can now build both Eclipse plugins and RCP app with the 'hacked' mojo. > > Good luck to all Eclipse with maven builders. > Jeroen. > > > Jeroen Lankheet wrote: > > > > Hi Amit, > > > > The problem was detected reviously and filed under > > http://jira.codehaus.org/browse/MOJO-738 > > I solved the problem as follows: > > 1. I checked out version 6085 of the trunk of the pde-maven-plugin. I > used > > this specific version because I'm using Eclipse 3.3 with maven 2.0.8 on > > Windows. > > 2. I changed "zip" in EclipsePDEAttachMojo.java to "jar" > > 3. I changed the ".zip" in line 226 of EclipsePDEMojo.java to ".jar" and > > line 236 to "clean build.update.jar" > > 4. I built the 'damn' thing: mvn clean install > > 5. I ignored the build error because of test failures > > 6. I grabbed the class files and updated the pde-maven-plugin jar with > > these class files. > > When I build my Eclipse plugin I now have a jar archive installed in my > > project directory and in the local repository. > > > > This is not a proper way of working. To my opinion, building the type of > > archive should be configurable in the POM, and not fixed in the code as > it > > is now, but at least it's working for me now. > > > > One more thing. The PDE plugin may also be used to build an RCP > > application. The fix I mention here will not work for RCP, but the > > alpha-2-SNAPSHOT version will. > > > > Regards, > > Jeroen > > > > > > amit kumar-18 wrote: > >> > >> Hi Jeroren, > >> I spent almost a week on avoiding that src.zip in the plugin.zip. I did > >> not > >> find any help on that and ultimately I had to resolve to a workaround > >> which > >> is that I now build a feature(dummy) which includes the plug in I > >> actually > >> want to build. When I get the feature.zip, I find my plug in inside > that > >> without src.zip. > >> > >> I know its not something I should have resolved to, but that was the > only > >> thing that I could find to fix the src.zip problem. > >> > >> If you find something on how to correct the ant calls, please let me > know > >> as > >> well. > >> > >> > >> Thanks and regards, > >> Amit Kumar > >> > >> On Mon, Mar 17, 2008 at 6:40 PM, JeroenL <[EMAIL PROTECTED]> wrote: > >> > >>> > >>> Hi all, > >>> > >>> I'm trying to build an Eclipse plugin with maven. > >>> Problems are that 1) the archive is zipped and 2) a directory is added > >>> and > >>> 3) a sr.zip is added. > >>> After investigating the calls to Ant I discovered that maven calls the > >>> targets "clean build.jars zip.plugin". > >>> According my belief this should be "clean build.update.jar" > >>> Does anyone have an idea how to call the proper targets? > >>> > >>> Regards, > >>> Jeroen > >>> -- > >>> View this message in context: > >>> > http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16092576.html > >>> Sent from the Maven - Users mailing list archive at Nabble.com. > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16138073.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Customizing Build order
How to list that dependency? I do have the dependency of A3 on B1 and B2(in the tag as jar). But that doesn't seems to make Maven go to build B1 and B2 when building A3 because I guess it looks in the repository, if not there it throws an error. If it has been working in this way, it would have been the solution. But I am not able to see that happening. Is there a different way of mentioning a project As' dependency on another projectB that would trigger the build of projectB as soon as it finds in the dependencies? of that project? Regards, Amit. On Wed, Mar 19, 2008 at 6:49 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Maven starts with the ordering listed in the poms (A and its children, > then B and its children, etc) unless there is a dependency. If it sees a > dependency, then it will automatically reorder by pushing down modules > that have a dependency so they build after their dep. > > I'm wondering why the order matters if you don't have a dependency > listed (I'm assuming you don't or it would be ordered already). > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 18, 2008 4:42 AM > To: Maven Users List > Subject: Customizing Build order > > Hi, > I have a multi-module project with the following structure. > > Root > -A > -A1 > -A2 > -A3 > -B > -B1 > -B2 > -B3 > -B4 > > > In the Root's pom i have mentioned my modules as: > A > B > > Now is there a way that I can change the normal build order(which is) > > -Root > -A > -A1 > -A2 > -A3 > -B > -B1 > -B2 > -B3 > -B4 > > > to something like > > -Root > -A > -A1 > -A2 > -B > -B1 > -B2 > -A3 > -B4 > > It is actually a requirement. But I doubt that there is a possibility > that > the CVS structure itself is not competent enough then to handle > inter-module > dependencies. > > Any inputs? > > Thanks and regards, > Amit Kumar > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Suppressing the logging in PDE build.
Hi, I am building my eclipse build using pde-maven-plugin. Is there anyway I can suppress the warnings and Info logging that happens on the screen? Regards, Amit
Re: Customizing Build order
Oh Okay. Yes simon you are right. Thanks for the advise. Regards, Amit On Tue, Mar 18, 2008 at 3:46 PM, David Delbecq <[EMAIL PROTECTED]> wrote: > En l'instant précis du 18/03/08 09:42, amit kumar s'exprimait en ces > termes: > > Hi, > > I have a multi-module project with the following structure. > > > > Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > In the Root's pom i have mentioned my modules as: > > A > > B > > > > Now is there a way that I can change the normal build order(which is) > > > > -Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > to something like > > > > -Root > > -A > > -A1 > > -A2 > > -B > > -B1 > > -B2 > > -A3 > > -B4 > > > > It is actually a requirement. But I doubt that there is a possibility > that > > the CVS structure itself is not competent enough then to handle > inter-module > > dependencies. > > > > Any inputs? > > > > Thanks and regards, > > Amit Kumar > > > > > In the A3 project, add dependencies that point to all other projects you > need to have compiled before (i suspect you need B2 resources for A3?), > maven should order them properly. > > -- > David Delbecq > Institut Royal Météorologique > Ext:557 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Customizing Build order
Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: A B Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar
Re: pde-maven-plugin calls wrong ant target
Hi Jeroren, I spent almost a week on avoiding that src.zip in the plugin.zip. I did not find any help on that and ultimately I had to resolve to a workaround which is that I now build a feature(dummy) which includes the plug in I actually want to build. When I get the feature.zip, I find my plug in inside that without src.zip. I know its not something I should have resolved to, but that was the only thing that I could find to fix the src.zip problem. If you find something on how to correct the ant calls, please let me know as well. Thanks and regards, Amit Kumar On Mon, Mar 17, 2008 at 6:40 PM, JeroenL <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm trying to build an Eclipse plugin with maven. > Problems are that 1) the archive is zipped and 2) a directory is added and > 3) a sr.zip is added. > After investigating the calls to Ant I discovered that maven calls the > targets "clean build.jars zip.plugin". > According my belief this should be "clean build.update.jar" > Does anyone have an idea how to call the proper targets? > > Regards, > Jeroen > -- > View this message in context: > http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16092576.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Problem with snapshots
Owing to amateurism I have configured the repository with snapshots at two places, in the pom.xml and in settings.xml. It has been working fine for me. Will try playing around with it and let you know. Regards, Amit Kumar On Wed, Mar 5, 2008 at 6:20 AM, Papapara Tudu <[EMAIL PROTECTED]> wrote: > > > amit kumar-18 wrote: > > > > You mean even from the local repository the maven is not able to pick up > > the > > latest of the jars? > > > Yes, that's the problem - I can see that the latest jars are downloaded to > my local repository, but they aren't used for the compiled war and ear > files. > > Cheers, > Papapara Tudu > -- > View this message in context: > http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15848863.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Problem with snapshots
You mean even from the local repository the maven is not able to pick up the latest of the jars? Regards, Amit On Tue, Mar 4, 2008 at 8:50 PM, Papapara Tudu <[EMAIL PROTECTED]> wrote: > > > amit kumar-18 wrote: > > > > Well I faced a similar problem but configuring my remote repository for > > snapshots worked for me. I had to add the below to my repository > > > > > > my-internal-site > > file:///192.168.x.x/Repository > > > > true > > always > > warn > > > > > > > > I started getting latest of the jars present under the project-SNAPSHOT > > folder in the repository. > > > > > > I tried two configurations: > 1. using my local repository both for releases and snapshots > 2. having a separate local repo for releases and a separate one for > snapshots. > > Both results were identical though :( > > Papapara Tudu > > -- > View this message in context: > http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15829527.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Add .classes to compilation classpath
Okay. Then you can jar up the classes as told by Simon and install/deploy(look for command mvn install:install-file... or mvn deploy:deploy-file...) them to your repository. There are few jar files which are not outcome of maven projects but yet we are using at out place. This seems to be the simplest of the options. On Tue, Mar 4, 2008 at 4:58 PM, <[EMAIL PROTECTED]> wrote: > Oh sorry, > > I meant to include some .class files from some other projects > which are not maven projects and they can not be easily installed > as maven packages. I think it would be possible to use ant plugin but it > should > be something much simpler I guess? > > Thanks > > > Quoting amit kumar <[EMAIL PROTECTED]>: > > > I had concept/misconception that target/classes gets added to the > classpath > > by maven as default? > > > > Are you dealing with generated sources? > > > > Regards, > > Amit > > > > On Tue, Mar 4, 2008 at 4:34 PM, <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi everybody, > > > > > > I'm new to maven. I have a simple question that I can't find an answer > > > anywhere: > > > I want to include additional classes in the classpath while compiling > my > > > project > > > but I can't find any > > > obvious solution for this. > > > > > > - The classes I want to include can not be installed in a maven > repository > > > - I tried the compiler plugin by adding > > > true > > > > > >myDic/classes > > > > > > but this doesn't seem to work. > > > > > > Any suggestions? > > > Thanks > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Add .classes to compilation classpath
I had concept/misconception that target/classes gets added to the classpath by maven as default? Are you dealing with generated sources? Regards, Amit On Tue, Mar 4, 2008 at 4:34 PM, <[EMAIL PROTECTED]> wrote: > > Hi everybody, > > I'm new to maven. I have a simple question that I can't find an answer > anywhere: > I want to include additional classes in the classpath while compiling my > project > but I can't find any > obvious solution for this. > > - The classes I want to include can not be installed in a maven repository > - I tried the compiler plugin by adding > true > >myDic/classes > > but this doesn't seem to work. > > Any suggestions? > Thanks > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Problem with snapshots
Well I faced a similar problem but configuring my remote repository for snapshots worked for me. I had to add the below to my repository my-internal-site file:///192.168.x.x/Repository true always warn I started getting latest of the jars present under the project-SNAPSHOT folder in the repository. Hope this works for you as well. Regards, Amit Kumar 2008/3/4 Jeff MAURY <[EMAIL PROTECTED]>: > Can you submit your output with -X option ? > > Jeff MAURY > > On Tue, Mar 4, 2008 at 11:35 AM, Papapara Tudu < > [EMAIL PROTECTED]> > wrote: > > > > > I just wanted to bring this topic up again as I still don't know what > the > > reason for my problem is. Does anyone have any other ideas? Thanks! > > > > Cheers, > > Papapara Tudu > > -- > > View this message in context: > > > http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15824504.html > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > La mélancolie c'est communiste > Tout le monde y a droit de temps en temps > La mélancolie n'est pas capitaliste > C'est même gratuit pour les perdants > La mélancolie c'est pacifiste > On ne lui rentre jamais dedans > La mélancolie oh tu sais ça existe > Elle se prend même avec des gants > La mélancolie c'est pour les syndicalistes > Il faut juste sa carte de permanent > > Miossec (2006) > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com >
Re: PDE Plugin
Hi, I keep on seeing the below log every time I build my plug-in from command line: [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied. [eclipse.buildScript] Bundle org.eclipse.gmf.bridge.ui.dashboard: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.bridge.ui.dashboard_1.0.100.v20061222-1800 [eclipse.buildScript] Bundle org.eclipse.gmf.bridge.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.bridge.ui_1.0.100.v20061214- [eclipse.buildScript] Bundle org.eclipse.gmf.codegen.edit: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen.edit_1.2.1.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.codegen.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen.ui_1.1.0.v20061222-1800 [eclipse.buildScript] Optional plug-in org.eclipse.gmf.bridge.trace_[1.0.0 ,2.0.0) is not availble. [eclipse.buildScript] Bundle org.eclipse.gmf.codegen: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen_1.2.1.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.doc.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.doc.ui_1.0.0.v20061214- [eclipse.buildScript] Bundle org.eclipse.gmf.doc: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.doc_1.0.0.v20061214- [eclipse.buildScript] Bundle org.eclipse.gmf.ecore.editor: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.ecore.editor_1.0.100.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.graphdef.codegen.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.graphdef.codegen.ui_1.0.102.v20061214- [eclipse.buildScript] Bundle org.eclipse.gmf.graphdef.codegen: .. .. .. Would this create any problem at the run-time? I am facing problems with the build plugin at the the time of testing, its behaving weird. Does this has something to do with the above log messages? Thanks in advance. Been stuck on this for two days now :( Regards, Amit On Fri, Feb 22, 2008 at 7:18 PM, amit kumar <[EMAIL PROTECTED]> wrote: > Hi, > But I had checked some plugins that gets shipped with eclipse (3.3) for > instance org.apache.batik_1.6.0.v20061222-1222, they do have a lib folder > inside them but their Manifest.mf file looks a little different, it > doesn't have an entry for Bundle.classpath, rather it has mentioned many > packages in Export Packages. > > What could be the case with that plugin? Is it because they are not using > maven? or something else? Just curious. > > > Regards, > Amit > > > On Fri, Feb 22, 2008 at 6:37 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > > > amit kumar wrote: > > > > > Copying the dependencies to the root file is what has worked till now. > > But > > > the ultimate packaged plug in looks a little messy. So I was just > > trying to > > > do accomplish the copying of dependency to the lib folder as an > > > improvisation. > > > > The need to copy the dependencies to the root folder comes about due to > > an Eclipse bug - The Eclipse IDE has a feature that allows you to add > > "links" to dependencies, and the Eclipse IDE puts these in links in the > > root of the project. > > > > Unfortunately this linked dependencies feature is not mirrored in the > > ant based Eclipse PDE build code, which takes the existence of the files > > literally. If the files aren't physically in the root directory, then > > the PDE build will fail. > > > > You may also encounter this in Eclipse on it's own: your project may > > build and run fine from within the IDE, but when you run "export your > > product" the Eclipse build mysteriously fails. > > > > Regards, > > Graham > > -- > > > >
Re: SNAPSHOT
Hi,
Got it resolved. Actually I was using jboss-sar packaging for my project and
addition to that I was also using copy-dependencies, which was not required
since jboss-sar plugin also copies the dependencies to lib folder.
This was creating the problem.
I had removed copy-dependencies now and it seems to work fine.
Regards,
Amit
On Tue, Feb 26, 2008 at 12:50 PM, amit kumar <[EMAIL PROTECTED]>
wrote:
> This is happening for jboss-sar packaging. And I see these two versions
> only at the time of "adding entry" while building jar.
>
> [DEBUG] adding entry lib/dependency-1.0.0-20080226.053600-13.jar
> [DEBUG] adding entry lib/dependency-1.0.0-SNAPSHOT.jar
>
>
> On Tue, Feb 26, 2008 at 12:45 PM, amit kumar <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> > >
> >
> >
> > > Now this is a new problem, I am seeing the dependency getting packaged
> > > as dependency-1.0.0-SNAPSHOT.jar as well as
> > > dependency-1.0.0-TIMESTAMP.jar
> > > I am using copy-dependency to copy the dependencies to a lib folder.
> > > How to overcome this?
> > >
> > > This is my configuration:
> > >
> > >
> > > ${project.build.directory}/${project.artifactId}-${
> > > project.version}/lib
> > > false
> > > false
> > > true
> > > true
> > >
> > >
> > > I tried turning true also
> > > but not working. Any help?
> > >
> > > Regards,
> > > Amit
> > >
> >
> > >
> > > On Mon, Feb 18, 2008 at 7:48 PM, Sebastien Brunot <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > >
> > > > This is indeed a buggy feature: the retrieved snpashot dependency,
> > > > in
> > > > the case of a war module for example, is sometime included as
> > > > mydependency-1.0-SNAPSHOT.jar, and sometimes as
> > > > mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a
> > > > dependency
> > > > can also be included twice as mydependency-1.0-TIMESTAMP1.jar and
> > > > mydependency-1.0-TIMESTAMP2.jar.
> > > >
> > > > My two cents,
> > > >
> > > > Sebastien
> > > >
> > > > -Original Message-
> > > > From: amit kumar [mailto:[EMAIL PROTECTED]
> > > > Sent: Monday, February 18, 2008 09:52
> > > > To: Maven Users List
> > > > Subject: Re: SNAPSHOT
> > > >
> > > > It seems to work for me. Whenever a new SNAPSHOT version(
> > > > 1.0.0-SNAPSHOT)
> > > > is deployed to the reposiroty maven stores it with timestamp witn in
> > > > the
> > > > 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar
> > > > keeps on getting updated corresponding to the latest deployed jar.
> > > > So in the repository the 1.0.0-SNAPSHOT folder has all the so far
> > > > deployed jar files along with the timestamp and a
> > > > artifact-1.0.0-SNAPSHOT.jar, which gets retrieved.
> > > >
> > > >
> > > > Regards,
> > > > Amit
> > > >
> > > >
> > > > On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > If my maven2 repository persists each artifact with time stamp
> > > > as
> > > > > > part of their filename, is SNAPSHOT version still going to work?
> > > > >
> > > > > Yes. It uses the metadata file in the repository to decide which
> > > > > timestamped file to retrieve.
> > > > >
> > > > > (Are you using just 'SNAPSHOT' as a version? Usually it's
> > > > > 1.0-SNAPSHOT or similar.)
> > > > >
> > > > > --
> > > > > Wendy
> > > > >
> > > > >
> > > > -
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> >
>
Re: Problem with maven-dependency-plugin: copy-dependencies
Hi,
Got it resolved. Actually I was using jboss-sar packaging for my project and
addition to that I was also using copy-dependencies, which was not required
since jboss-sar plugin also copies the dependencies to lib folder.
This was creating the problem.
I had removed copy-dependencies now and it seems to work fine.
Thanks and regards,
Amit
On Tue, Feb 26, 2008 at 1:59 PM, Stephen Connolly <
[EMAIL PROTECTED]> wrote:
> Have you been doing a build clean?
>
> If you don't do a clean build then artifacts from the previous build can
> end
> up hanging around
>
> -Stephen
>
> On Tue, Feb 26, 2008 at 7:11 AM, amit kumar <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> > Now this is a new problem, I am seeing the dependency getting packaged
> as
> > dependency-1.0.0-SNAPSHOT.jar as well as dependency-1.0.0-TIMESTAMP.jar
> > I am using copy-dependency to copy the dependencies to a lib folder. How
> > to
> > overcome this?
> >
> > This is my configuration:
> >
> >
> > ${project.build.directory}/${project.artifactId}-${
> > project.version}/lib
> > false
> > false
> > true
> > true
> >
> >
> > I tried turning true also but
> > not
> > working. Any help?
> >
> > Regards,
> > Amit
> >
> >
> > On Tue, Feb 26, 2008 at 12:29 PM, amit kumar <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Oh Ok. Thanks.
> > >
> > >
> > > On Tue, Feb 26, 2008 at 4:33 AM, Brian E. Fox <
> [EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > The dependency plugin only copies things. It's up to whatever is
> doing
> > > > the packaging to create the manifest.
> > > >
> > > > -Original Message-
> > > > From: amit kumar [mailto:[EMAIL PROTECTED]
> > > > Sent: Friday, February 22, 2008 1:37 AM
> > > > To: Maven Users List
> > > > Subject: Re: Problem with maven-dependency-plugin: copy-dependencies
> > > >
> > > > Can I modify Manifest entries along with the copy-dependencies goal
> in
> > > > configuration? Or something like that. I want the Manifest.mf to
> have
> > > > entries for the copied dependencies(in the specific folder).
> > > >
> > > >
> > > > Regards,
> > > > Amit Kumar
> > > >
> > > > On Wed, Jan 2, 2008 at 2:18 PM, PatrickV
> > > > <[EMAIL PROTECTED]>
> > > > wrote:
> > > >
> > > > >
> > > > > The attachments are there. My first posting did indeed not include
> > the
> > > > > attachements, I edited the posting and now the file (pp.zip) is
> > there.
> > > > >
> > > > >
> > > > >
> > > > > Brian E Fox wrote:
> > > > > >
> > > > > > The attachments didn't come through. Try writing a jira at
> > > > > > http://jira.codehaus.org/browse/MDEP and attach the files there.
> > > > > >
> > > > > > -Original Message-
> > > > > > From: PatrickV [mailto:[EMAIL PROTECTED]
> > > > > > Sent: Tuesday, January 01, 2008 11:08 AM
> > > > > > To: users@maven.apache.org
> > > > > > Subject: RE: Problem with maven-dependency-plugin:
> > copy-dependencies
> > > > > >
> > > > > >
> > > > > > I hope I can make it clear by attaching the pom's to this
> message.
> > > > The
> > > > > > poms
> > > > > > are stripped versions of the real stuff.
> > > > > >
> > > > > > Module A = pp-common.xml
> > > > > > Module B = pp-client.xml
> > > > > > Module C = pp-server.xml
> > > > > >
> > > > > > The copy dependencies plugin is stated in pp-server.xml.
> > > > > > pp-server depends on pp-common and pp-client.
> > > > > >
> > > > > > I expect to see after running the copy-dependency goal to target
> > > > > > directory:
> > > > > >
> > > > > > pp-common.jar in target directory
> > > > > > pp-client.jar in target directory
> > > > > > all dependencies from pp-server
> > > > > > all dependencies from pp-common not yet included in target
> > directory
> > > > > &
Re: SNAPSHOT
This is happening for jboss-sar packaging. And I see these two versions only
at the time of "adding entry" while building jar.
[DEBUG] adding entry lib/dependency-1.0.0-20080226.053600-13.jar
[DEBUG] adding entry lib/dependency-1.0.0-SNAPSHOT.jar
On Tue, Feb 26, 2008 at 12:45 PM, amit kumar <[EMAIL PROTECTED]>
wrote:
> Hi,
> >
>
>
> > Now this is a new problem, I am seeing the dependency getting packaged
> > as dependency-1.0.0-SNAPSHOT.jar as well as
> > dependency-1.0.0-TIMESTAMP.jar
> > I am using copy-dependency to copy the dependencies to a lib folder. How
> > to overcome this?
> >
> > This is my configuration:
> >
> >
> > ${project.build.directory}/${project.artifactId}-${
> > project.version}/lib
> > false
> > false
> > true
> > true
> >
> >
> > I tried turning true also but
> > not working. Any help?
> >
> > Regards,
> > Amit
> >
>
> >
> > On Mon, Feb 18, 2008 at 7:48 PM, Sebastien Brunot <[EMAIL PROTECTED]>
> > wrote:
> >
> > >
> > > This is indeed a buggy feature: the retrieved snpashot dependency, in
> > > the case of a war module for example, is sometime included as
> > > mydependency-1.0-SNAPSHOT.jar, and sometimes as
> > > mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a
> > > dependency
> > > can also be included twice as mydependency-1.0-TIMESTAMP1.jar and
> > > mydependency-1.0-TIMESTAMP2.jar.
> > >
> > > My two cents,
> > >
> > > Sebastien
> > >
> > > -Original Message-
> > > From: amit kumar [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, February 18, 2008 09:52
> > > To: Maven Users List
> > > Subject: Re: SNAPSHOT
> > >
> > > It seems to work for me. Whenever a new SNAPSHOT version(
> > > 1.0.0-SNAPSHOT)
> > > is deployed to the reposiroty maven stores it with timestamp witn in
> > > the
> > > 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar
> > > keeps on getting updated corresponding to the latest deployed jar.
> > > So in the repository the 1.0.0-SNAPSHOT folder has all the so far
> > > deployed jar files along with the timestamp and a
> > > artifact-1.0.0-SNAPSHOT.jar, which gets retrieved.
> > >
> > >
> > > Regards,
> > > Amit
> > >
> > >
> > > On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > If my maven2 repository persists each artifact with time stamp as
> > > > > part of their filename, is SNAPSHOT version still going to work?
> > > >
> > > > Yes. It uses the metadata file in the repository to decide which
> > > > timestamped file to retrieve.
> > > >
> > > > (Are you using just 'SNAPSHOT' as a version? Usually it's
> > > > 1.0-SNAPSHOT or similar.)
> > > >
> > > > --
> > > > Wendy
> > > >
> > > >
> > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
Re: SNAPSHOT
>
> Hi,
>
> Now this is a new problem, I am seeing the dependency getting packaged as
> dependency-1.0.0-SNAPSHOT.jar as well as dependency-1.0.0-TIMESTAMP.jar
> I am using copy-dependency to copy the dependencies to a lib folder. How
> to overcome this?
>
> This is my configuration:
>
>
> ${project.build.directory}/${project.artifactId}-${
> project.version}/lib
> false
> false
> true
> true
>
>
> I tried turning true also but
> not working. Any help?
>
> Regards,
> Amit
>
>
> On Mon, Feb 18, 2008 at 7:48 PM, Sebastien Brunot <[EMAIL PROTECTED]> wrote:
>
> >
> > This is indeed a buggy feature: the retrieved snpashot dependency, in
> > the case of a war module for example, is sometime included as
> > mydependency-1.0-SNAPSHOT.jar, and sometimes as
> > mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a dependency
> > can also be included twice as mydependency-1.0-TIMESTAMP1.jar and
> > mydependency-1.0-TIMESTAMP2.jar.
> >
> > My two cents,
> >
> > Sebastien
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Monday, February 18, 2008 09:52
> > To: Maven Users List
> > Subject: Re: SNAPSHOT
> >
> > It seems to work for me. Whenever a new SNAPSHOT version(1.0.0-SNAPSHOT)
> > is deployed to the reposiroty maven stores it with timestamp witn in the
> > 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar
> > keeps on getting updated corresponding to the latest deployed jar.
> > So in the repository the 1.0.0-SNAPSHOT folder has all the so far
> > deployed jar files along with the timestamp and a
> > artifact-1.0.0-SNAPSHOT.jar, which gets retrieved.
> >
> >
> > Regards,
> > Amit
> >
> >
> > On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > >
> > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote:
> > >
> > > > If my maven2 repository persists each artifact with time stamp as
> > > > part of their filename, is SNAPSHOT version still going to work?
> > >
> > > Yes. It uses the metadata file in the repository to decide which
> > > timestamped file to retrieve.
> > >
> > > (Are you using just 'SNAPSHOT' as a version? Usually it's
> > > 1.0-SNAPSHOT or similar.)
> > >
> > > --
> > > Wendy
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
Re: Problem with maven-dependency-plugin: copy-dependencies
Hi,
Now this is a new problem, I am seeing the dependency getting packaged as
dependency-1.0.0-SNAPSHOT.jar as well as dependency-1.0.0-TIMESTAMP.jar
I am using copy-dependency to copy the dependencies to a lib folder. How to
overcome this?
This is my configuration:
${project.build.directory}/${project.artifactId}-${
project.version}/lib
false
false
true
true
I tried turning true also but not
working. Any help?
Regards,
Amit
On Tue, Feb 26, 2008 at 12:29 PM, amit kumar <[EMAIL PROTECTED]>
wrote:
> Oh Ok. Thanks.
>
>
> On Tue, Feb 26, 2008 at 4:33 AM, Brian E. Fox <[EMAIL PROTECTED]>
> wrote:
>
> > The dependency plugin only copies things. It's up to whatever is doing
> > the packaging to create the manifest.
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Friday, February 22, 2008 1:37 AM
> > To: Maven Users List
> > Subject: Re: Problem with maven-dependency-plugin: copy-dependencies
> >
> > Can I modify Manifest entries along with the copy-dependencies goal in
> > configuration? Or something like that. I want the Manifest.mf to have
> > entries for the copied dependencies(in the specific folder).
> >
> >
> > Regards,
> > Amit Kumar
> >
> > On Wed, Jan 2, 2008 at 2:18 PM, PatrickV
> > <[EMAIL PROTECTED]>
> > wrote:
> >
> > >
> > > The attachments are there. My first posting did indeed not include the
> > > attachements, I edited the posting and now the file (pp.zip) is there.
> > >
> > >
> > >
> > > Brian E Fox wrote:
> > > >
> > > > The attachments didn't come through. Try writing a jira at
> > > > http://jira.codehaus.org/browse/MDEP and attach the files there.
> > > >
> > > > -Original Message-
> > > > From: PatrickV [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, January 01, 2008 11:08 AM
> > > > To: users@maven.apache.org
> > > > Subject: RE: Problem with maven-dependency-plugin: copy-dependencies
> > > >
> > > >
> > > > I hope I can make it clear by attaching the pom's to this message.
> > The
> > > > poms
> > > > are stripped versions of the real stuff.
> > > >
> > > > Module A = pp-common.xml
> > > > Module B = pp-client.xml
> > > > Module C = pp-server.xml
> > > >
> > > > The copy dependencies plugin is stated in pp-server.xml.
> > > > pp-server depends on pp-common and pp-client.
> > > >
> > > > I expect to see after running the copy-dependency goal to target
> > > > directory:
> > > >
> > > > pp-common.jar in target directory
> > > > pp-client.jar in target directory
> > > > all dependencies from pp-server
> > > > all dependencies from pp-common not yet included in target directory
> > > > all dependencies from pp-client not yet included in target directory
> > > >
> > > > What I do see in target directory
> > > > all dependencies from pp-server
> > > > all dependencies from pp-common
> > > > all dependencies from pp-client
> > > > BUT NOT... pp-common.jar and pp-client.jar, allthough they too ARE
> > > > listed in
> > > > the dependencies of the pp-server project.
> > > >
> > > > Packaging of pp-server (war or jar) has no influence on result.
> > > >
> > > > The process is triggered by executing mvn -U clean package on
> > parent.
> > > >
> > > > I hope the issue is clear now.
> > > >
> > > > KR
> > > >
> > > > PatrickV
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Brian E Fox wrote:
> > > >>
> > > >>
> > > >>
> > > >> -Original Mes http://www.nabble.com/file/p14567676/pp.zip
> > pp.zip
> > > >> sage-
> > > >> From: PatrickV [mailto:[EMAIL PROTECTED]
> > > >> Sent: Sunday, December 30, 2007 2:11 PM
> > > >> To: users@maven.apache.org
> > > >> Subject: RE: Problem with maven-dependency-plugin:
> > copy-dependencies
> > > >>
> > > >>
> > > >>>I changed the packaging of module C into jar, and no difference.
> > > >>>I think the copy-dependency plugin
Re: Problem with maven-dependency-plugin: copy-dependencies
Oh Ok. Thanks. On Tue, Feb 26, 2008 at 4:33 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The dependency plugin only copies things. It's up to whatever is doing > the packaging to create the manifest. > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Friday, February 22, 2008 1:37 AM > To: Maven Users List > Subject: Re: Problem with maven-dependency-plugin: copy-dependencies > > Can I modify Manifest entries along with the copy-dependencies goal in > configuration? Or something like that. I want the Manifest.mf to have > entries for the copied dependencies(in the specific folder). > > > Regards, > Amit Kumar > > On Wed, Jan 2, 2008 at 2:18 PM, PatrickV > <[EMAIL PROTECTED]> > wrote: > > > > > The attachments are there. My first posting did indeed not include the > > attachements, I edited the posting and now the file (pp.zip) is there. > > > > > > > > Brian E Fox wrote: > > > > > > The attachments didn't come through. Try writing a jira at > > > http://jira.codehaus.org/browse/MDEP and attach the files there. > > > > > > -Original Message- > > > From: PatrickV [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, January 01, 2008 11:08 AM > > > To: users@maven.apache.org > > > Subject: RE: Problem with maven-dependency-plugin: copy-dependencies > > > > > > > > > I hope I can make it clear by attaching the pom's to this message. > The > > > poms > > > are stripped versions of the real stuff. > > > > > > Module A = pp-common.xml > > > Module B = pp-client.xml > > > Module C = pp-server.xml > > > > > > The copy dependencies plugin is stated in pp-server.xml. > > > pp-server depends on pp-common and pp-client. > > > > > > I expect to see after running the copy-dependency goal to target > > > directory: > > > > > > pp-common.jar in target directory > > > pp-client.jar in target directory > > > all dependencies from pp-server > > > all dependencies from pp-common not yet included in target directory > > > all dependencies from pp-client not yet included in target directory > > > > > > What I do see in target directory > > > all dependencies from pp-server > > > all dependencies from pp-common > > > all dependencies from pp-client > > > BUT NOT... pp-common.jar and pp-client.jar, allthough they too ARE > > > listed in > > > the dependencies of the pp-server project. > > > > > > Packaging of pp-server (war or jar) has no influence on result. > > > > > > The process is triggered by executing mvn -U clean package on > parent. > > > > > > I hope the issue is clear now. > > > > > > KR > > > > > > PatrickV > > > > > > > > > > > > > > > > > > Brian E Fox wrote: > > >> > > >> > > >> > > >> -Original Mes http://www.nabble.com/file/p14567676/pp.zip > pp.zip > > >> sage- > > >> From: PatrickV [mailto:[EMAIL PROTECTED] > > >> Sent: Sunday, December 30, 2007 2:11 PM > > >> To: users@maven.apache.org > > >> Subject: RE: Problem with maven-dependency-plugin: > copy-dependencies > > >> > > >> > > >>>I changed the packaging of module C into jar, and no difference. > > >>>I think the copy-dependency plugin does not take into account > > >> dependencies > > >>>on artifacts on the reactor (in this case Module A and Module B), > but > > >> only > > >>>on "real" dependencies from the repositorie. > > >> > > >> Not sure what you mean here. If a dependency is listed in the pom, > it > > > is > > >> included. There are no other ways for dependencies to be included. > > >> Sharing a reactor has other subtle effects but doesn't change the > fact > > >> that a dependency needs to be listed. Perhaps I'm not getting what > > >> you're saying. > > >> > > >> "...I don't want to pull in the dependencies of Module C (the war), > > > but > > >> I want to copy all the dependencies > > >> of Module C (including Module A and Module B).." > > >> > > >> Huh? You do or don't want the dependencies of Module C? > > >> > > >> "to
Re: Why is there two configuration files for Maven, settings.xml and pom.xml
Hi, I am facing this problem after I put information about my Intranet repository in my settings.xml in .m2 folder. I had to do this, because m2eclipse which has the value for local settings file from \m2\settings.xml , wasn't able to download the SNAPSHOT versions from remote Intranet repository, if they were not present in the local repository(I had to configure the repository or snapshots). Everything seemed to work fine until I had to add other repository in my pom.xml(specific to the project), I added codehaus snapshots repository, but settings.xml seems to override everything now and throws an error telling could not download the required plug in from "internal-site". One way that I could thought of was to add this repository as well in the settings.xml but even after adding the error was same. Am I inferring the right reason for this or there is something else that I am not able to figure out? Could someone please guide on the same? Regards, Amit Kumar On Mon, Feb 25, 2008 at 10:17 AM, Allen, Daniel <[EMAIL PROTECTED]> wrote: > The idea is that some settings are not specific to a project > (settings.xml is just a file on your computer, not part of the build). > For example, one thing I have in settings.xml is settings for my local > web proxy. That doesn't make any sense to attach to your project, since > it's probably not applicable to everyone who wants to build said > project. And conversely, I don't have to add that to every single > project I ever try to build. > > There is some flexibility in putting certain things in either the POM or > settings.xml. You can create profiles in settings.xml, for example. This > is so that, again, you can deal with build aspects peculiar to your > particular machine. It's a fine line, but there's a pretty good page[1] > that details the concerns with putting profiles into settings.xml > without breaking portability. Or you can just see for yourself what can > go in the POM [2] and what can go in the settings [3]. > > ~Dan Allen > > > [1] > http://maven.apache.org/guides/introduction/introduction-to-profiles.htm > l > [2] http://maven.apache.org/ref/2.0.8/maven-model/maven.html - pom.xml > structre > [3] http://maven.apache.org/ref/2.0.8/maven-settings/settings.html - > settings.xml structure > -Original Message- > From: youhaodeyi [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 24, 2008 2:54 AM > To: users@maven.apache.org > Subject: Why is there two configuration files for Maven, settings.xml > and pom.xml > > > Can I put the configurations in settings.xml to pom.xml? Why does maven > use > two configuration files? > > -- > This message may contain confidential, proprietary, or legally privileged > information. No confidentiality or privilege is waived by any transmission > to an unintended recipient. If you are not an intended recipient, please > notify the sender and delete this message immediately. Any views expressed > in this message are those of the sender, not those of any entity within the > KBC Financial Products group of companies (together referred to as "KBC > FP"). > > This message does not create any obligation, contractual or otherwise, on > the part of KBC FP. It is not an offer (or solicitation of an offer) of, or > a recommendation to buy or sell, any financial product. Any prices or other > values included in this message are indicative only, and do not necessarily > represent current market prices, prices at which KBC FP would enter into a > transaction, or prices at which similar transactions may be carried on KBC > FP's own books. The information contained in this message is provided "as > is", without representations or warranties, express or implied, of any kind. > Past performance is not indicative of future returns. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: SNAPSHOT
Hi Sebastien, Even I just realized this problem with SNAPSHOT dependencies in my EAR project, some of them I am getting as mydependency-1.0-SNAPSHOT.jar and some of them as mydependency-1.0-TIMESTAMP.jar, is there any workaround for this? Or some problem with the configuration in settings.xml? or somewhere? Regards, Amit On Mon, Feb 18, 2008 at 7:48 PM, Sebastien Brunot <[EMAIL PROTECTED]> wrote: > > This is indeed a buggy feature: the retrieved snpashot dependency, in > the case of a war module for example, is sometime included as > mydependency-1.0-SNAPSHOT.jar, and sometimes as > mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a dependency > can also be included twice as mydependency-1.0-TIMESTAMP1.jar and > mydependency-1.0-TIMESTAMP2.jar. > > My two cents, > > Sebastien > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 18, 2008 09:52 > To: Maven Users List > Subject: Re: SNAPSHOT > > It seems to work for me. Whenever a new SNAPSHOT version(1.0.0-SNAPSHOT) > is deployed to the reposiroty maven stores it with timestamp witn in the > 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar > keeps on getting updated corresponding to the latest deployed jar. > So in the repository the 1.0.0-SNAPSHOT folder has all the so far > deployed jar files along with the timestamp and a > artifact-1.0.0-SNAPSHOT.jar, which gets retrieved. > > > Regards, > Amit > > > On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote: > > > > > If my maven2 repository persists each artifact with time stamp as > > > part of their filename, is SNAPSHOT version still going to work? > > > > Yes. It uses the metadata file in the repository to decide which > > timestamped file to retrieve. > > > > (Are you using just 'SNAPSHOT' as a version? Usually it's > > 1.0-SNAPSHOT or similar.) > > > > -- > > Wendy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: PDE Plugin
Hi, But I had checked some plugins that gets shipped with eclipse (3.3) for instance org.apache.batik_1.6.0.v20061222-1222, they do have a lib folder inside them but their Manifest.mf file looks a little different, it doesn't have an entry for Bundle.classpath, rather it has mentioned many packages in Export Packages. What could be the case with that plugin? Is it because they are not using maven? or something else? Just curious. Regards, Amit On Fri, Feb 22, 2008 at 6:37 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > amit kumar wrote: > > > Copying the dependencies to the root file is what has worked till now. > But > > the ultimate packaged plug in looks a little messy. So I was just trying > to > > do accomplish the copying of dependency to the lib folder as an > > improvisation. > > The need to copy the dependencies to the root folder comes about due to > an Eclipse bug - The Eclipse IDE has a feature that allows you to add > "links" to dependencies, and the Eclipse IDE puts these in links in the > root of the project. > > Unfortunately this linked dependencies feature is not mirrored in the > ant based Eclipse PDE build code, which takes the existence of the files > literally. If the files aren't physically in the root directory, then > the PDE build will fail. > > You may also encounter this in Eclipse on it's own: your project may > build and run fine from within the IDE, but when you run "export your > product" the Eclipse build mysteriously fails. > > Regards, > Graham > -- >
Re: Problem with maven-dependency-plugin: copy-dependencies
Thanks. Amit Kumar On Fri, Feb 22, 2008 at 2:30 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > amit kumar wrote: > > > Can I modify Manifest entries along with the copy-dependencies goal in > > configuration? Or something like that. I want the Manifest.mf to have > > entries for the copied dependencies(in the specific folder). > > Do it the other way around - don't try and change the path in the > manifest, the plugin won't let you. Change the location of where the > dependency plugin puts the jars. > > Regards, > Graham > -- >
Re: PDE Plugin
Copying the dependencies to the root file is what has worked till now. But the ultimate packaged plug in looks a little messy. So I was just trying to do accomplish the copying of dependency to the lib folder as an improvisation. Thanks and Regards, Amit On Fri, Feb 22, 2008 at 2:26 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > amit kumar wrote: > > > With the help of people here especially Graham, I am able to build the > plug > > in successfully using pde-maven-plugin. The only thing left now is that > I > > want to package the lib folder along with the plugin, which I can do by > > using copy-dependency but I am not able the lib entries to Manifest file > > thus leaving the plug in handicapped at run time. The manifest entries > tell > > plug in to expect the dependencies in the root folder of plugin, while I > > want to package it in lib folder(the tidier option). > > Tell the dependency plugin to copy the dependencies into the root > folder, not the lib folder. > > Full instructions on how to do that are here: > > http://maven.apache.org/plugins/maven-eclipse-plugin/pde.html > > Regards, > Graham > -- >
Re: maven-eclipse-plugin writes to src/main/webapp
On synchronizing a pde plugin with maven-eclipse-plugin, it looks to me that Manifest.mf file do get synchronized even though it is in META-INF folder. Does maven-eclipse-plugin synchronizes it with .classpath or how? Regards, Amit On Fri, Feb 22, 2008 at 1:13 PM, Martin Höller <[EMAIL PROTECTED]> wrote: > On Thursday 21 February 2008 wrote Arnaud HERITIER: > > I prefer to have a new issue and a link between them. > > Created: http://jira.codehaus.org/browse/MECLIPSE-392 > > > You can wait to have it fixed OR you can propose a patch (code+test+doc) > > to be sure it will be. > > Currently I'm too busy but maybe I'll have a look at it later... > > thx, > - martin > -- > Martin Höller | [EMAIL PROTECTED] > *x Software + Systeme | http://www.xss.co.at/ > Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 > A-1100 Vienna, Austria | Fax: +43-1-6060114-71 >
Re: Problem with maven-dependency-plugin: copy-dependencies
Can I modify Manifest entries along with the copy-dependencies goal in configuration? Or something like that. I want the Manifest.mf to have entries for the copied dependencies(in the specific folder). Regards, Amit Kumar On Wed, Jan 2, 2008 at 2:18 PM, PatrickV <[EMAIL PROTECTED]> wrote: > > The attachments are there. My first posting did indeed not include the > attachements, I edited the posting and now the file (pp.zip) is there. > > > > Brian E Fox wrote: > > > > The attachments didn't come through. Try writing a jira at > > http://jira.codehaus.org/browse/MDEP and attach the files there. > > > > -Original Message- > > From: PatrickV [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 01, 2008 11:08 AM > > To: users@maven.apache.org > > Subject: RE: Problem with maven-dependency-plugin: copy-dependencies > > > > > > I hope I can make it clear by attaching the pom's to this message. The > > poms > > are stripped versions of the real stuff. > > > > Module A = pp-common.xml > > Module B = pp-client.xml > > Module C = pp-server.xml > > > > The copy dependencies plugin is stated in pp-server.xml. > > pp-server depends on pp-common and pp-client. > > > > I expect to see after running the copy-dependency goal to target > > directory: > > > > pp-common.jar in target directory > > pp-client.jar in target directory > > all dependencies from pp-server > > all dependencies from pp-common not yet included in target directory > > all dependencies from pp-client not yet included in target directory > > > > What I do see in target directory > > all dependencies from pp-server > > all dependencies from pp-common > > all dependencies from pp-client > > BUT NOT... pp-common.jar and pp-client.jar, allthough they too ARE > > listed in > > the dependencies of the pp-server project. > > > > Packaging of pp-server (war or jar) has no influence on result. > > > > The process is triggered by executing mvn -U clean package on parent. > > > > I hope the issue is clear now. > > > > KR > > > > PatrickV > > > > > > > > > > > > Brian E Fox wrote: > >> > >> > >> > >> -Original Mes http://www.nabble.com/file/p14567676/pp.zip pp.zip > >> sage- > >> From: PatrickV [mailto:[EMAIL PROTECTED] > >> Sent: Sunday, December 30, 2007 2:11 PM > >> To: users@maven.apache.org > >> Subject: RE: Problem with maven-dependency-plugin: copy-dependencies > >> > >> > >>>I changed the packaging of module C into jar, and no difference. > >>>I think the copy-dependency plugin does not take into account > >> dependencies > >>>on artifacts on the reactor (in this case Module A and Module B), but > >> only > >>>on "real" dependencies from the repositorie. > >> > >> Not sure what you mean here. If a dependency is listed in the pom, it > > is > >> included. There are no other ways for dependencies to be included. > >> Sharing a reactor has other subtle effects but doesn't change the fact > >> that a dependency needs to be listed. Perhaps I'm not getting what > >> you're saying. > >> > >> "...I don't want to pull in the dependencies of Module C (the war), > > but > >> I want to copy all the dependencies > >> of Module C (including Module A and Module B).." > >> > >> Huh? You do or don't want the dependencies of Module C? > >> > >> "to a specific directory, so that later on I can do some additional > >> processing on it. All dependencies > >> are there, even the transitive dependencies of module A and module B > >> (which > >> are both packaged as Jar), except for ModuleA.jar and ModuleB.jar." > >> > >> Simply binding copy-dependencies should get you all dependencies of > >> whatever pom you've put it in. If it's module C, then you'll get all > >> transitive dependencies of that Module. If you put it in the parent, > >> chances are that parent doesn't declare dependencies like you want so > >> you won't get what you want (module != dependency). > >> > >> Brian E Fox wrote: > >>> > >>> I think the problem is the war packaging. Maven doesn't normally pull > >> in > >>> war dependencies transitively because the dependencies are included > >>> insid
Re: PDE Plugin
With the help of people here especially Graham, I am able to build the plug
in successfully using pde-maven-plugin. The only thing left now is that I
want to package the lib folder along with the plugin, which I can do by
using copy-dependency but I am not able the lib entries to Manifest file
thus leaving the plug in handicapped at run time. The manifest entries tell
plug in to expect the dependencies in the root folder of plugin, while I
want to package it in lib folder(the tidier option).
Could someone please help on that?
Regards,
Amit Kumar
On Wed, Feb 20, 2008 at 3:14 PM, amit kumar <[EMAIL PROTECTED]>
wrote:
> Thanks Dan, but these files are already in eclipse and I just need to copy
> them to the final zipped file.(The outcome of pde-maven-plugin).
>
> Thanks for the kind help. Would look into it.
>
> Regards,
> Amit
>
>
> On Feb 20, 2008 2:55 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> > again pde plugin knows nothing about maven pom's resource, you will
> > need some help from antrun plugin to copy those files to
> > a place eclipse can pickup.
> >
> > About the source, you will need to lookup how eclipse's ant build
> > their stuff, there must by a property
> > you can passing into ant build via pde plugin
> >
> > On Feb 20, 2008 1:16 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> > > Hi Dan,
> > > Thanks for valuable pointers , now its able to compile the source
> > using
> > > dependencies from both Plugin Dependencies part and pom.xml. Still
> > there are
> > > few doubts and issues
> > >
> > > 1) pde-plugin is also zipping the source in the zip file that it
> > packages
> > > out of the project. Is there a way to avoid this?
> > >
> > > 2) Resources folders seems to be not working when pde-maven-plugin is
> > being
> > > used, I tried packaging plugin.properties and message.properties(two
> > of the
> > > required files). But I can't see them in the final zipped file.
> > >
> > > I tried
> > >
> > >
> > >
> > > ${basedir}/resources
> > > /
> > >
> > >
> > >
> > > and as well as
> > >
> > >
> > >
> > > ${basedir}
> > >
> > > plugin.properties
> > > message.properties.properties
> > >
> > >
> > > **/*.java
> > >
> > > /
> > >
> > >
> > >
> > > But both seems to be not working.
> > >
> > > 3) Is it possible to bundle the pom.xml dependencies along with the
> > zipped
> > > file as well?
> > > It is a requirement that the pom.xml dependency jar files must be
> > bundled
> > > with the plugin(zip/jar) inside a lib folder or something of that
> > sort.
> > >
> > >
> > > Thanks and Regards,
> > > Amit
> > >
> > >
> > >
> > >
> > > On Feb 19, 2008 4:29 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > >
> > > > The question here is how do you want pde plugin to consume your
> > pom's
> > > > dependencies thru a way that eclipse can understand?
> > > >
> > > > I maven-dependency-plugin to copy my dependencies to a place that
> > > > eclispe's pde can pick up.
> > > >
> > > > -D
> > > >
> > > > On Feb 19, 2008 2:42 AM, amit kumar <[EMAIL PROTECTED]>
> > wrote:
> > > > > Oh Ok. But how to inform pde-maven-plugin about the declared
> > > > dependencies? I
> > > > > mean is there any configuration that I am missing?
> > > > >
> > > > > Thanks and regards,
> > > > > Amit
> > > > >
> > > > >
> > > > > On Feb 19, 2008 3:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > pde-maven-plugin does not know about your declared dependencies
> > in
> > > > > > pom.xml. Every thing must still going thru the eclipse way.
> > > > > >
> > > > > > -D
> > > > > >
> > > > > > On Feb 19, 2008 12:50 AM, amit kumar <[EMAIL PROTECTED]>
> > > > wrote:
> > > > > > > Hi!
> > > > > > > I am trying to use maven-pde-plugin but without any succes
Adding a folder to classpath at runtime
Hi,
Is it possible to add a newly created folder(and its contents) to the
classpath at the runtime(on the fly) using maven.
I am using this pde-maven-plugin where I am copying the dependencies to the
lib folder inside the ${basedir} and wants it to be available while
compiling the source code.
Any help?
Regards,
Amit
Re: PDE Plugin
Thanks Dan, but these files are already in eclipse and I just need to copy
them to the final zipped file.(The outcome of pde-maven-plugin).
Thanks for the kind help. Would look into it.
Regards,
Amit
On Feb 20, 2008 2:55 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> again pde plugin knows nothing about maven pom's resource, you will
> need some help from antrun plugin to copy those files to
> a place eclipse can pickup.
>
> About the source, you will need to lookup how eclipse's ant build
> their stuff, there must by a property
> you can passing into ant build via pde plugin
>
> On Feb 20, 2008 1:16 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> > Hi Dan,
> > Thanks for valuable pointers , now its able to compile the source using
> > dependencies from both Plugin Dependencies part and pom.xml. Still there
> are
> > few doubts and issues
> >
> > 1) pde-plugin is also zipping the source in the zip file that it
> packages
> > out of the project. Is there a way to avoid this?
> >
> > 2) Resources folders seems to be not working when pde-maven-plugin is
> being
> > used, I tried packaging plugin.properties and message.properties(two of
> the
> > required files). But I can't see them in the final zipped file.
> >
> > I tried
> >
> >
> >
> > ${basedir}/resources
> > /
> >
> >
> >
> > and as well as
> >
> >
> >
> > ${basedir}
> >
> > plugin.properties
> > message.properties.properties
> >
> >
> > **/*.java
> >
> > /
> >
> >
> >
> > But both seems to be not working.
> >
> > 3) Is it possible to bundle the pom.xml dependencies along with the
> zipped
> > file as well?
> > It is a requirement that the pom.xml dependency jar files must be
> bundled
> > with the plugin(zip/jar) inside a lib folder or something of that sort.
> >
> >
> > Thanks and Regards,
> > Amit
> >
> >
> >
> >
> > On Feb 19, 2008 4:29 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > The question here is how do you want pde plugin to consume your pom's
> > > dependencies thru a way that eclipse can understand?
> > >
> > > I maven-dependency-plugin to copy my dependencies to a place that
> > > eclispe's pde can pick up.
> > >
> > > -D
> > >
> > > On Feb 19, 2008 2:42 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> > > > Oh Ok. But how to inform pde-maven-plugin about the declared
> > > dependencies? I
> > > > mean is there any configuration that I am missing?
> > > >
> > > > Thanks and regards,
> > > > Amit
> > > >
> > > >
> > > > On Feb 19, 2008 3:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > pde-maven-plugin does not know about your declared dependencies in
> > > > > pom.xml. Every thing must still going thru the eclipse way.
> > > > >
> > > > > -D
> > > > >
> > > > > On Feb 19, 2008 12:50 AM, amit kumar <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > Hi!
> > > > > > I am trying to use maven-pde-plugin but without any success.
> > > > > > When I do mvn install to a plug in project, maven-pde-plugin is
> not
> > > able
> > > > > to
> > > > > > resolve the pom.xml's dependencies.
> > > > > > I am unable to locate any relevant document over net.
> > > > > >
> > > > > > Could someone please help me? It has been continuously 2nd day
> when
> > > I am
> > > > > > stuck with it.
> > > > > >
> > > > > > The build.xml that maven-pde-plugin is generating doesn't have
> the
> > > > > pom.xml's
> > > > > > dependenies in the classpath items. It has only the Plugin
> > > dependenies.
> > > > > >
> > > > > > Is there any workaround for the same?
> > > > > >
> > > > > > As linked to by Dan I tried
> > > > > >
> http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.htmlthis
> > > > > as
> > > > > > well. Any plugin with only plugin dependencies is working fine,
> but
> > > as
> > &
Re: PDE Plugin
Hi Dan,
Thanks for valuable pointers , now its able to compile the source using
dependencies from both Plugin Dependencies part and pom.xml. Still there are
few doubts and issues
1) pde-plugin is also zipping the source in the zip file that it packages
out of the project. Is there a way to avoid this?
2) Resources folders seems to be not working when pde-maven-plugin is being
used, I tried packaging plugin.properties and message.properties(two of the
required files). But I can't see them in the final zipped file.
I tried
${basedir}/resources
/
and as well as
${basedir}
plugin.properties
message.properties.properties
**/*.java
/
But both seems to be not working.
3) Is it possible to bundle the pom.xml dependencies along with the zipped
file as well?
It is a requirement that the pom.xml dependency jar files must be bundled
with the plugin(zip/jar) inside a lib folder or something of that sort.
Thanks and Regards,
Amit
On Feb 19, 2008 4:29 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> The question here is how do you want pde plugin to consume your pom's
> dependencies thru a way that eclipse can understand?
>
> I maven-dependency-plugin to copy my dependencies to a place that
> eclispe's pde can pick up.
>
> -D
>
> On Feb 19, 2008 2:42 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> > Oh Ok. But how to inform pde-maven-plugin about the declared
> dependencies? I
> > mean is there any configuration that I am missing?
> >
> > Thanks and regards,
> > Amit
> >
> >
> > On Feb 19, 2008 3:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > pde-maven-plugin does not know about your declared dependencies in
> > > pom.xml. Every thing must still going thru the eclipse way.
> > >
> > > -D
> > >
> > > On Feb 19, 2008 12:50 AM, amit kumar <[EMAIL PROTECTED]>
> wrote:
> > > > Hi!
> > > > I am trying to use maven-pde-plugin but without any success.
> > > > When I do mvn install to a plug in project, maven-pde-plugin is not
> able
> > > to
> > > > resolve the pom.xml's dependencies.
> > > > I am unable to locate any relevant document over net.
> > > >
> > > > Could someone please help me? It has been continuously 2nd day when
> I am
> > > > stuck with it.
> > > >
> > > > The build.xml that maven-pde-plugin is generating doesn't have the
> > > pom.xml's
> > > > dependenies in the classpath items. It has only the Plugin
> dependenies.
> > > >
> > > > Is there any workaround for the same?
> > > >
> > > > As linked to by Dan I tried
> > > > http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.htmlthis
> > > as
> > > > well. Any plugin with only plugin dependencies is working fine, but
> as
> > > soon
> > > > as I describe dependencies in pom.xml compilation errors start
> coming
> > > owing
> > > > to the non availability of the dependencies in the jar file.
> > > >
> > > >
> > > > Many thanks in anticipation.
> > > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > On Feb 13, 2008 2:48 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > IT = integration test
> > > > >
> > > > > try this
> > > http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html
> > > > >
> > > > > On Feb 13, 2008 12:54 AM, amit kumar <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > Pardon me Dan, but I did not get it? IT tests?
> > > > > >
> > > > > >
> > > > > > On Feb 13, 2008 1:27 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > > are you able to try other IT tests?
> > > > > > >
> > > > > > > On Feb 12, 2008 11:17 PM, amit kumar <
> [EMAIL PROTECTED]>
> > > > > wrote:
> > > > > > > > Hi,
> > > > > > > > No one has any idea of the problem? I am still awfully stuck
> > > with
> > > > > PDE
> > > > > > > plug
> > > > > > > > in and not able to build eclipse plugin projects using it.
> Could
> > > > > someone
> > > &
Re: A question about the user list
Thank you. I would look into the Nabble option. On Feb 19, 2008 7:55 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > amit kumar schrieb: > > Hi, > > I am confused on how to reply to a thread that was there even before I > > subscribed to this user list? Can someone please help me on that? > > > Most of the apache lists are archived by Nabble. If you have a Nabble > account then you can just click on the archived message to reply > in-thread. > > Threads are just implemented by sending a mail with the "In-Reply-To" > header referring to the original mail. > So theoretically it is possible to reply to an email as long as you know > the id of the original mail. But I don't know of any email clients that > allow that to be entered directly. > > Regards, > Simon > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
A question about the user list
Hi, I am confused on how to reply to a thread that was there even before I subscribed to this user list? Can someone please help me on that? Regards, Amit
Re: PDE Plugin
Oh Ok. But how to inform pde-maven-plugin about the declared dependencies? I mean is there any configuration that I am missing? Thanks and regards, Amit On Feb 19, 2008 3:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > pde-maven-plugin does not know about your declared dependencies in > pom.xml. Every thing must still going thru the eclipse way. > > -D > > On Feb 19, 2008 12:50 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > Hi! > > I am trying to use maven-pde-plugin but without any success. > > When I do mvn install to a plug in project, maven-pde-plugin is not able > to > > resolve the pom.xml's dependencies. > > I am unable to locate any relevant document over net. > > > > Could someone please help me? It has been continuously 2nd day when I am > > stuck with it. > > > > The build.xml that maven-pde-plugin is generating doesn't have the > pom.xml's > > dependenies in the classpath items. It has only the Plugin dependenies. > > > > Is there any workaround for the same? > > > > As linked to by Dan I tried > > http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html this > as > > well. Any plugin with only plugin dependencies is working fine, but as > soon > > as I describe dependencies in pom.xml compilation errors start coming > owing > > to the non availability of the dependencies in the jar file. > > > > > > Many thanks in anticipation. > > > > Regards, > > > > > > > > On Feb 13, 2008 2:48 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > > > IT = integration test > > > > > > try this > http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html > > > > > > On Feb 13, 2008 12:54 AM, amit kumar <[EMAIL PROTECTED]> > wrote: > > > > Pardon me Dan, but I did not get it? IT tests? > > > > > > > > > > > > On Feb 13, 2008 1:27 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > > > > > > > are you able to try other IT tests? > > > > > > > > > > On Feb 12, 2008 11:17 PM, amit kumar <[EMAIL PROTECTED]> > > > wrote: > > > > > > Hi, > > > > > > No one has any idea of the problem? I am still awfully stuck > with > > > PDE > > > > > plug > > > > > > in and not able to build eclipse plugin projects using it. Could > > > someone > > > > > > please help? > > > > > > Any aware of any helpful content regarding the same? > > > > > > > > > > > > > > > > > > Please. > > > > > > > > > > > > Regards, > > > > > > Amit > > > > > > > > > > > > > > > > > > On Feb 12, 2008 11:09 AM, amit kumar <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > > > > > While following the tutorial at pde-maven-plugin page. When I > > > tried to > > > > > > > run "mvn install" I am getting the following errors: > > > > > > > > > > > > > > [ERROR] BUILD ERROR > > > > > > > [INFO] > > > > > > > > > > > > > > > > > > > > > > > [INFO] Compilation failure > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[3,34] > > > > > > > package org.eclipse.jface.resource does not exist > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[4,29] > > > > > > > package org.eclipse.ui.plugin does not exist > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[5,26] > > > > > > > package org.osgi.framework does not exist > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > E:\Eclipse\workspace\PDE_Plugin_Tutorial\plug
Re: PDE Plugin
Hi!
I am trying to use maven-pde-plugin but without any success.
When I do mvn install to a plug in project, maven-pde-plugin is not able to
resolve the pom.xml's dependencies.
I am unable to locate any relevant document over net.
Could someone please help me? It has been continuously 2nd day when I am
stuck with it.
The build.xml that maven-pde-plugin is generating doesn't have the pom.xml's
dependenies in the classpath items. It has only the Plugin dependenies.
Is there any workaround for the same?
As linked to by Dan I tried
http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html this as
well. Any plugin with only plugin dependencies is working fine, but as soon
as I describe dependencies in pom.xml compilation errors start coming owing
to the non availability of the dependencies in the jar file.
Many thanks in anticipation.
Regards,
On Feb 13, 2008 2:48 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> IT = integration test
>
> try this http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html
>
> On Feb 13, 2008 12:54 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> > Pardon me Dan, but I did not get it? IT tests?
> >
> >
> > On Feb 13, 2008 1:27 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > are you able to try other IT tests?
> > >
> > > On Feb 12, 2008 11:17 PM, amit kumar <[EMAIL PROTECTED]>
> wrote:
> > > > Hi,
> > > > No one has any idea of the problem? I am still awfully stuck with
> PDE
> > > plug
> > > > in and not able to build eclipse plugin projects using it. Could
> someone
> > > > please help?
> > > > Any aware of any helpful content regarding the same?
> > > >
> > > >
> > > > Please.
> > > >
> > > > Regards,
> > > > Amit
> > > >
> > > >
> > > > On Feb 12, 2008 11:09 AM, amit kumar <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > > > While following the tutorial at pde-maven-plugin page. When I
> tried to
> > > > > run "mvn install" I am getting the following errors:
> > > > >
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO]
> > > > >
> > >
>
> > > > > [INFO] Compilation failure
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[3,34]
> > > > > package org.eclipse.jface.resource does not exist
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[4,29]
> > > > > package org.eclipse.ui.plugin does not exist
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[5,26]
> > > > > package org.osgi.framework does not exist
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[10,31]
> > > > > cannot find symbol
> > > > > symbol: class AbstractUIPlugin
> > > > > public class Activator extends AbstractUIPlugin {
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[28,26]
> > > > > cannot find symbol
> > > > > symbol : class BundleContext
> > > > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[37,25]
> > > > > cannot find symbol
> > > > > symbol : class BundleContext
> > > > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > > > >
> > > > >
> > > > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[58,22]
> > > > > cannot find symbol
> > > > > symbol : class ImageDescriptor
> > > > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > > > >
> > >
Re: site:site unable to find parent...
Is parent's pom in repository? I too had faced similar problem(not with
site), then after help from user list I installed the Parent's pom as well
in the repository(local/remote) with install/deploy.
It solved the problem for me after that.
Regards,
Amit
On Feb 19, 2008 9:18 AM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
> Hi Lee,
>
> I think by default the relative path is ../pom.xml which is ok unless you
> have a flat (eclipse friendly) structure like we do. So you probably don't
> need it set.
>
> Yes I most certainly have in my parent.
>
> From the logs tho, it is using the parent ${basedir} even when it is
> within
> a module.
>
> I will try to install as a hacky workaround in the meantime
>
>
> Cheers!!!
>
>
> On Feb 19, 2008 10:45 AM, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> > Sad ... replying to myself.
> >
> > I noticed one thing when I read the Jira issue Andrew linked to.
> >
> > When doing the "site" you have to do "install site" to make it work
> unless
> > you did an "install" since the last change to the parent pom.
> >
> > -- lee
> >
> > On Feb 18, 2008 6:10 PM, Lee Meador <[EMAIL PROTECTED]> wrote:
> >
> > > Are you using this in the parent pom?
> > >
> > > ../module-1
> > >
> > > As I remember, this works if done some ways.
> > >
> > > You can build if you issue 'mvn' from /parent mostly
> > > You can build if you issue "mvn -f parent/pom.xml" from the folder
> above
> > > all the project folders mostly
> > > You can build if you issue 'mvn' from /module-1 but it will only build
> > > that project and has some caveats below.
> > >
> > > I think the first 2 only work if you have done 'install' recently. (
> i.e.
> > > Since changes to the pom.xml in the parent)
> > > I think the last one only works if you did one of the first two with a
> > > recent install (possibly with -N option to only build the parent)
> > >
> > > I'm using maven version 2.0.7 right now. I think these rules were
> > accurate
> > > in version 2.0.4.
> > >
> > > And, I just noticed, I don't use the tag. Maybe that's
> a
> > > killer for you.
> > >
> > > -- Lee
> > >
> > >
> > > On Feb 18, 2008 5:39 PM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
> > >
> > > > This is a known issue:
> > > > http://jira.codehaus.org/browse/MSITE-261
> > > >
> > > >
> > > > On Feb 19, 2008 9:36 AM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi Hi,
> > > > >
> > > > > This is the error I am getting which is causing my sites to
> > > > > build/behave badly. The model file path is wrong in the log below,
> > and
> > > > the
> > > > > project is "unknown"... not sure why any of this is happening
> > > > >
> > > > > [INFO] [site:site]
> > > > > [INFO] Unable to load parent project from a relative path: Could
> not
> > > > find
> > > > > the model file '/data/workspaces/mycompany/parent/../pom.xml'. for
> > > > project
> > > > > unknown
> > > > > [INFO] Parent project loaded from repository.
> > > > >
> > > > > This is my structure
> > > > >
> > > > > /myproject/parent/pom.xml
> > > > > /myproject/module-1/pom.xml
> > > > > /myproject/module-2/pom.xml
> > > > > /myproject/module-3/pom.xml
> > > > >
> > > > >
> > > > > This is my inside each module-X
> > > > >
> > > > > myproject
> > > > > parent
> > > > > 0.0.1-SNAPSHOT
> > > > > ../parent/pom.xml
> > > > >
> > > > >
> > > > > Any help would be great!!! :)
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > -- Lee Meador
> > > Sent from gmail. My real email address is lee AT leemeador.com
> >
> >
> >
> >
> > --
> > -- Lee Meador
> > Sent from gmail. My real email address is lee AT leemeador.com
> >
>
Re: SNAPSHOT
It seems to work for me. Whenever a new SNAPSHOT version(1.0.0-SNAPSHOT) is deployed to the reposiroty maven stores it with timestamp witn in the 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar keeps on getting updated corresponding to the latest deployed jar. So in the repository the 1.0.0-SNAPSHOT folder has all the so far deployed jar files along with the timestamp and a artifact-1.0.0-SNAPSHOT.jar, which gets retrieved. Regards, Amit On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote: > > > If my maven2 repository persists each artifact with time stamp as part > > of their filename, is SNAPSHOT version still going to work? > > Yes. It uses the metadata file in the repository to decide which > timestamped file to retrieve. > > (Are you using just 'SNAPSHOT' as a version? Usually it's > 1.0-SNAPSHOT or similar.) > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven Concepts
Thanks Wayne. The problem seems to be resolved. Regards, Amit On Fri, Feb 15, 2008 at 9:26 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > I think your problem is as follows: > > Maven regards 1.0.0-SNAPSHOT as "before" 1.0.0. > Also Maven does not necessarily use the version you've declared. The > version tag is really more of a hint or suggestion than an absolute > requirement. (Unless you've "locked down" your versions.) > Thus, although you have a declared dependency on 1.0.0-SNAPSHOT, Maven > sees the 1.0.0 release version and uses it instead. > > I would suggest simply bumping the version to 1.0.1-SNAPSHOT. > Or perhaps using [1.0.0-SNAPSHOT] in your > dependency declaration. That will force Maven to use the snapshot and > not the release. > > In the future, do not number things like this. Snapshot always comes > before a release, and then you bump the version and make another > Snapshot. > > Wayne > > On 2/15/08, amit kumar <[EMAIL PROTECTED]> wrote: > > Thanks simon I will take care for the selection of threads in > > future.Apologies for the same. > > > > > > > > On Fri, Feb 15, 2008 at 1:28 PM, Mark Struberg <[EMAIL PROTECTED]> > wrote: > > > > > The only reason i can think of to have a snapshot repo in a company is > to > > > get rid of very old > > > snapshots which may bump up your repo size heavily. It is much easier > to > > > drop obsolete snapshots > > > if they are strictly separated from released modules. > > > > > > LieGrü, > > > strub > > > > > > --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> schrieb: > > > > Hi Amit, > > > > > > > > Firstly, when you have a question that is not really related to an > > > > existing thread, then please start a new email thread rather than > > > > replying to the existing one. By doing that, and choosing a good > subject > > > > line for the email, other people with the same problem can later > search > > > > the email archives and find the necessary answer. > > > > > > > > AFAIK, there's no major problem having release and snapshot versions > in > > > > the same repository. > > > > > > > > This doesn't happen often with open-source projects because (a) all > > > > releases get put into the official repositories (ibiblio, > > > > rep1.maven.org) that are mirrored arround the world, and (b) > mirroring > > > > snapshots is silly. So for apache software for example, there is a > > > > non-mirrored repo that only holds snapshots, with all actual > releases > > > > going to the mirrored repos. > > > > > > > > But for a company that doesn't mirror its releases, I'm not aware of > any > > > > reason why snapshots and releases cannot be on the same repo. > > > > > > > > Your problem is probably that you have the tag that > points > > > > to your repo configured with snapshot-lookup disabled. Try adding > this > > > > to the repository tag: > > > > > > > >true > > > > > > > > > > > > Regards, > > > > Simon > > > > > > > > amit kumar schrieb: > > > > > SNAPSHOT Vs release version. > > > > > > > > > > Hi, > > > > > In our intranet maven repository we have both release version and > > > snaphot > > > > > version under the same groupId (under the same folder on file > system). > > > While > > > > > amounting to ignorance to SNAPSHOT versions, release version > existed > > > long > > > > > before SNAPSHOT versions started getting placed in the same > folder. > > > > > Now we realized that when people changed their dependency versions > to > > > > > snapshot, maven is not able to fetch the SNAPSHOT version, and it > just > > > tells > > > > > not able to find the specified jar. > > > > > > > > > > The earlier dependency of y on x > > > > > > > > > > com.group.x > > > > > x > > > > > 1.0.0 > > > > > > > > > > has become > > > > > com.group.x > > > > > x > > > > > 1.0.0-SNAPSHOT > > > > > > > > > > and x has already been deployed to the repository with > > > > > 1.0.0-SNAPSHOTversion. Could someone please help me figure out > what > > > > > exactly is happening > > > > > here? > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > Lesen Sie Ihre E-Mails auf dem Handy. > > > www.yahoo.de/go > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Sending email notification to Owners
Hi! I have configured the email notifier in every pom.xml for respective module but it is just not happening. No Clue? My pom.xml looks like below : continuum http://192.168.0.100:8080/continuum mail true true false false [EMAIL PROTECTED] Continuum does show this as a notifier from Project in the Notifiers Display. But is just not sending the mail to this address, while it does send a mail to the Continuum Added modifiers. Although I have a multi-module project but because loading it recursively(Continuum Option)so do not have the option to set the notifiers from continuum separately. Any clue? Regards, Amit On Thu, Jan 24, 2008 at 7:24 PM, Jacob Northey <[EMAIL PROTECTED]> wrote: > > > Wendy Smoak-3 wrote: > > > > Perhaps you could suggest an enhancement for the notifier > > configuration, some way to tell it "send mail to all developers listed > > in this project". (Which immediately suggests that you should be able > > to send only to people with a certain role in the project...) > > > > How do we go about getting this change implemented? Taking what you > suggested, what I'd like to see is an additional role configuration for a > notifier: > > >... > > >developer > > > > > If nobody is available to work on this, or it isn't deemed high priority, > I'd be willing to implement it. Does this require a change in the POM > model > in maven? > > Jake > -- > View this message in context: > http://www.nabble.com/Sending-email-notification-to-Owners-tp14913326s177p15064207.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Surefire 2.4.1 classpath order
Hi, I have another related query regarding surefire, all of a sudden from today we started getting this error while executing JUnit tasks, the compilation of source file happens fine and the when compiling the test source files, the maven gives build failure telling that it was not able to load main class from C:\WINDOWS\TEMP\surefirebooter59557.jar What is going wrong here? Could someone please help on this? Regards, Amit On Fri, Feb 15, 2008 at 4:16 PM, Ben Lidgey <[EMAIL PROTECTED]> wrote: > Hi > > We are running tests using Surefire 2.4.1 and Maven 2.0.8. The Junit test > classes are expecting to load a properties file from src/test/resources with > the same name as a properties file in src/main/resources to load test data > etc. However the src/main/resources properties file is being loaded. > > Looking at the debug output shows: > > [DEBUG] Test Classpath : > [DEBUG] C:\Documents and > Settings\benl\.m2\repository\junit\junit\4.2\junit-4.2.jar > > [more jars] > > [DEBUG] c:\Development\Projects\MyProject\target\classes > [DEBUG] c:\Development\Projects\MyProject\target\test-classes > > Which would explain it. Is there anyway to get the test-classes before > classes in the classpath order? Setting childDelegation to true doesn't. > > Ben Lidgey > Senior Software Engineer > e: [EMAIL PROTECTED] > > Inuk Networks Limited > Enterprise House > Navigation Park > Abercynon > CF45 4SN > t: +44 (0)844 546 0100 > f: +44 (0)844 546 0200 > w: www.inuknetworks.com > > > This e-mail is confidential and intended solely for the use of the > individual(s) to whom it is addressed. Any views or opinions expressed are > those of the author. If you are not the intended recipient, please be > advised that any use, dissemination, printing or copying of this email is > strictly prohibited. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven Concepts
Thanks simon I will take care for the selection of threads in future.Apologies for the same. On Fri, Feb 15, 2008 at 1:28 PM, Mark Struberg <[EMAIL PROTECTED]> wrote: > The only reason i can think of to have a snapshot repo in a company is to > get rid of very old > snapshots which may bump up your repo size heavily. It is much easier to > drop obsolete snapshots > if they are strictly separated from released modules. > > LieGrü, > strub > > --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> schrieb: > > Hi Amit, > > > > Firstly, when you have a question that is not really related to an > > existing thread, then please start a new email thread rather than > > replying to the existing one. By doing that, and choosing a good subject > > line for the email, other people with the same problem can later search > > the email archives and find the necessary answer. > > > > AFAIK, there's no major problem having release and snapshot versions in > > the same repository. > > > > This doesn't happen often with open-source projects because (a) all > > releases get put into the official repositories (ibiblio, > > rep1.maven.org) that are mirrored arround the world, and (b) mirroring > > snapshots is silly. So for apache software for example, there is a > > non-mirrored repo that only holds snapshots, with all actual releases > > going to the mirrored repos. > > > > But for a company that doesn't mirror its releases, I'm not aware of any > > reason why snapshots and releases cannot be on the same repo. > > > > Your problem is probably that you have the tag that points > > to your repo configured with snapshot-lookup disabled. Try adding this > > to the repository tag: > > > >true > > > > > > Regards, > > Simon > > > > amit kumar schrieb: > > > SNAPSHOT Vs release version. > > > > > > Hi, > > > In our intranet maven repository we have both release version and > snaphot > > > version under the same groupId (under the same folder on file system). > While > > > amounting to ignorance to SNAPSHOT versions, release version existed > long > > > before SNAPSHOT versions started getting placed in the same folder. > > > Now we realized that when people changed their dependency versions to > > > snapshot, maven is not able to fetch the SNAPSHOT version, and it just > tells > > > not able to find the specified jar. > > > > > > The earlier dependency of y on x > > > > > > com.group.x > > > x > > > 1.0.0 > > > > > > has become > > > com.group.x > > > x > > > 1.0.0-SNAPSHOT > > > > > > and x has already been deployed to the repository with > > > 1.0.0-SNAPSHOTversion. Could someone please help me figure out what > > > exactly is happening > > > here? > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > Lesen Sie Ihre E-Mails auf dem Handy. > www.yahoo.de/go > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven Concepts
SNAPSHOT Vs release version.
Hi,
In our intranet maven repository we have both release version and snaphot
version under the same groupId (under the same folder on file system). While
amounting to ignorance to SNAPSHOT versions, release version existed long
before SNAPSHOT versions started getting placed in the same folder.
Now we realized that when people changed their dependency versions to
snapshot, maven is not able to fetch the SNAPSHOT version, and it just tells
not able to find the specified jar.
The earlier dependency of y on x
com.group.x
x
1.0.0
has become
com.group.x
x
1.0.0-SNAPSHOT
and x has already been deployed to the repository with
1.0.0-SNAPSHOTversion. Could someone please help me figure out what
exactly is happening
here?
Regards,
Amit
On Thu, Feb 14, 2008 at 3:17 PM, <[EMAIL PROTECTED]> wrote:
> You can add a property to your finalName and fill that with a profile, or
> use the build definition inside a profile to add your finalName to.
>
> Hth,
>
> Nick Stolwijk
>
> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
> Sent: Thu 2/14/2008 10:45
> To: Maven Users List
> Subject: Re: Maven Concepts
>
> *Different finalName for development and integration environment:
> Something like the builds at CI server would have x-INT-2008.jar.
> *
> Hi,
> The above is a requirement to be catered to. But my doubt is the finalName
> gets overridden in children projects if it is present(which is the case).
> How to accomplish this.
>
> Is profiles the answer?
>
> But submodules doesn't have a profile for finalName, they have it directly
> in the tag.
>
> Regards,
> Amit Kumar
>
>
> On Tue, Feb 12, 2008 at 9:49 PM, <[EMAIL PROTECTED]> wrote:
>
> > The modules section is only used when building an aggregate project. It
> is
> > not used for dependencies in any way. If submodule b uses submodule a,
> you
> > have to give submodule b a dependency on submodule a. If multiple
> submodules
> > depend on submodule a, you can have submodule a in the
> dependencyManagement,
> > with the right version (often it is ${project.version}, which is the
> > version of your aggregate project) so you don't need to include the
> version
> > number in each submodule.
> >
> > Hth,
> >
> > Nick Stolwijk
> >
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Tue 2/12/2008 15:15
> > To: Maven Users List
> > Subject: Re: Maven Concepts
> >
> > Continuing on the dependency Vs dependencyManagement, I read the
> documents
> > on it but after encountering the archetype:create for j2ee simple, I am
> > not
> > able to figure out what is the motive behind giving sub-modules of the
> > project in the dependencyManagement section.
> >
> >
> > Regards,
> > Amit
> >
> > On Feb 12, 2008 7:08 PM, amit kumar <[EMAIL PROTECTED]> wrote:
> >
> > > Thanks Nick. I was unaware of that part. Configured the repository for
> > > snapshots and now it is working.
> > >
> > > Regards,
> > > Amit
> > >
> > >
> > > On Feb 12, 2008 3:16 PM, <[EMAIL PROTECTED]> wrote:
> > >
> > > > How did you configure your repository? Especially take a look at the
> > > > updatePolicy element in your snapshot repository. [1] If this one is
> > > > omitted, it will default to "daily", so it is possible it won't take
> > your
> > > > newest snapshot. You can use "mvn -U" to look for newer versions of
> > the
> > > > snapshot dependencies. Or set the updatePolicy to another value:
> "The
> > > > frequency for downloading updates - can be "always", "daily"
> > (default),
> > > > "interval:XXX" (in minutes) or "never" (only if it doesn't exist
> > locally)."
> > > >
> > > > Hth,
> > > >
> > > > Nick S.
> > > >
> > > > [1]
> > > >
> >
> http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_snapshots
> > > >
> > > >
> > > > -Original Message-
> > > > From: amit kumar [mailto:[EMAIL PROTECTED]
> > > > Sent: Tue 2/12/2008 10:40
> > > > To: Maven Users List
> > > > Subject: Re: Maven Concepts
> > > >
> > > > I tested with SNAPSHOT version as well. But maven still seems to
> > prefer
> > > > the
> > > > local version of even the SNAPSH
Re: Maven Concepts
*Different finalName for development and integration environment:
Something like the builds at CI server would have x-INT-2008.jar.
*
Hi,
The above is a requirement to be catered to. But my doubt is the finalName
gets overridden in children projects if it is present(which is the case).
How to accomplish this.
Is profiles the answer?
But submodules doesn't have a profile for finalName, they have it directly
in the tag.
Regards,
Amit Kumar
On Tue, Feb 12, 2008 at 9:49 PM, <[EMAIL PROTECTED]> wrote:
> The modules section is only used when building an aggregate project. It is
> not used for dependencies in any way. If submodule b uses submodule a, you
> have to give submodule b a dependency on submodule a. If multiple submodules
> depend on submodule a, you can have submodule a in the dependencyManagement,
> with the right version (often it is ${project.version}, which is the
> version of your aggregate project) so you don't need to include the version
> number in each submodule.
>
> Hth,
>
> Nick Stolwijk
>
>
> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
> Sent: Tue 2/12/2008 15:15
> To: Maven Users List
> Subject: Re: Maven Concepts
>
> Continuing on the dependency Vs dependencyManagement, I read the documents
> on it but after encountering the archetype:create for j2ee simple, I am
> not
> able to figure out what is the motive behind giving sub-modules of the
> project in the dependencyManagement section.
>
>
> Regards,
> Amit
>
> On Feb 12, 2008 7:08 PM, amit kumar <[EMAIL PROTECTED]> wrote:
>
> > Thanks Nick. I was unaware of that part. Configured the repository for
> > snapshots and now it is working.
> >
> > Regards,
> > Amit
> >
> >
> > On Feb 12, 2008 3:16 PM, <[EMAIL PROTECTED]> wrote:
> >
> > > How did you configure your repository? Especially take a look at the
> > > updatePolicy element in your snapshot repository. [1] If this one is
> > > omitted, it will default to "daily", so it is possible it won't take
> your
> > > newest snapshot. You can use "mvn -U" to look for newer versions of
> the
> > > snapshot dependencies. Or set the updatePolicy to another value: "The
> > > frequency for downloading updates - can be "always", "daily"
> (default),
> > > "interval:XXX" (in minutes) or "never" (only if it doesn't exist
> locally)."
> > >
> > > Hth,
> > >
> > > Nick S.
> > >
> > > [1]
> > >
> http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_snapshots
> > >
> > >
> > > -Original Message-
> > > From: amit kumar [mailto:[EMAIL PROTECTED]
> > > Sent: Tue 2/12/2008 10:40
> > > To: Maven Users List
> > > Subject: Re: Maven Concepts
> > >
> > > I tested with SNAPSHOT version as well. But maven still seems to
> prefer
> > > the
> > > local version of even the SNAPSHOT version?
> > >
> > > i have these two modules a.jar and b.jar,
> > > a-1.0-SNAPSHOT.jar depends on b-1.0-SNAPSHOT.jar, I tested and
> deployed
> > > b.jar at a later time stamp and again tried to build a.jar. But still
> it
> > > fetched the local version which was build at 14:29 while the one of
> two
> > > jars
> > > at repository is a 14:45 built?
> > >
> > > Am I missing something here? I am using the buildNumber as well to
> have
> > > the
> > > finalName appended with time stamp.
> > >
> > > Regards,
> > > Amit
> > >
> > > On Feb 8, 2008 3:52 PM, Simon Kitching <[EMAIL PROTECTED]>
> wrote:
> > >
> > > > Stephen Connolly <[EMAIL PROTECTED]> schrieb:
> > > > > Redeploying a non-SNAPSHOT version is a _bad thing_ as Maven will
> > > not
> > > > > re-download it.
> > > >
> > > > Absolutely. Never overwrite an existing deployed file except when it
> > > has
> > > > SNAPSHOT in the version.
> > > >
> > > > Builds should be repeatable, ie you should be able to compile
> > > something
> > > > today, then compile it again next week and get the same result. This
> > > means
> > > > that stuff deployed to a repository should never change.
> > > >
> > > > The only exception is SNAPSHOT versions; when a project depends on
> one
> > > of
> > > > these, then it is explicitly acknowledging that repeatable builds
>
Re: PDE Plugin
Pardon me Dan, but I did not get it? IT tests?
On Feb 13, 2008 1:27 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> are you able to try other IT tests?
>
> On Feb 12, 2008 11:17 PM, amit kumar <[EMAIL PROTECTED]> wrote:
> > Hi,
> > No one has any idea of the problem? I am still awfully stuck with PDE
> plug
> > in and not able to build eclipse plugin projects using it. Could someone
> > please help?
> > Any aware of any helpful content regarding the same?
> >
> >
> > Please.
> >
> > Regards,
> > Amit
> >
> >
> > On Feb 12, 2008 11:09 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> >
> > > While following the tutorial at pde-maven-plugin page. When I tried to
> > > run "mvn install" I am getting the following errors:
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
>
> > > [INFO] Compilation failure
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[3,34]
> > > package org.eclipse.jface.resource does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[4,29]
> > > package org.eclipse.ui.plugin does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[5,26]
> > > package org.osgi.framework does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[10,31]
> > > cannot find symbol
> > > symbol: class AbstractUIPlugin
> > > public class Activator extends AbstractUIPlugin {
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[28,26]
> > > cannot find symbol
> > > symbol : class BundleContext
> > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[37,25]
> > > cannot find symbol
> > > symbol : class BundleContext
> > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[58,22]
> > > cannot find symbol
> > > symbol : class ImageDescriptor
> > > location: class test.pde_maven_plugin.simple_plugin.Activator
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[3,32]
> > > package org.eclipse.jface.action does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[4,33]
> > > package org.eclipse.jface.viewers does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[5,22]
> > > package org.eclipse.ui does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[6,22]
> > > package org.eclipse.ui does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[7,33]
> > > package org.eclipse.jface.dialogs does not exist
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[17,37]
> > > cannot find symbol
> > > symbol: class IWorkbenchWindowActionDelegate
> > > public class SampleAction implements IWorkbenchWindowActionDelegate {
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[18,16]
> > > cannot find symbol
> > > symbol : class IWorkbenchWindow
> > > location: class
> test.pde_maven_plugin.simple_plugin.actions.SampleAction
> > >
> > >
> > >
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\sim
Re: PDE Plugin
Hi,
No one has any idea of the problem? I am still awfully stuck with PDE plug
in and not able to build eclipse plugin projects using it. Could someone
please help?
Any aware of any helpful content regarding the same?
Please.
Regards,
Amit
On Feb 12, 2008 11:09 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> While following the tutorial at pde-maven-plugin page. When I tried to
> run "mvn install" I am getting the following errors:
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Compilation failure
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[3,34]
> package org.eclipse.jface.resource does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[4,29]
> package org.eclipse.ui.plugin does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[5,26]
> package org.osgi.framework does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[10,31]
> cannot find symbol
> symbol: class AbstractUIPlugin
> public class Activator extends AbstractUIPlugin {
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[28,26]
> cannot find symbol
> symbol : class BundleContext
> location: class test.pde_maven_plugin.simple_plugin.Activator
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[37,25]
> cannot find symbol
> symbol : class BundleContext
> location: class test.pde_maven_plugin.simple_plugin.Activator
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[58,22]
> cannot find symbol
> symbol : class ImageDescriptor
> location: class test.pde_maven_plugin.simple_plugin.Activator
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[3,32]
> package org.eclipse.jface.action does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[4,33]
> package org.eclipse.jface.viewers does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[5,22]
> package org.eclipse.ui does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[6,22]
> package org.eclipse.ui does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[7,33]
> package org.eclipse.jface.dialogs does not exist
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[17,37]
> cannot find symbol
> symbol: class IWorkbenchWindowActionDelegate
> public class SampleAction implements IWorkbenchWindowActionDelegate {
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[18,16]
> cannot find symbol
> symbol : class IWorkbenchWindow
> location: class test.pde_maven_plugin.simple_plugin.actions.SampleAction
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[31,24]
> cannot find symbol
> symbol : class IAction
> location: class test.pde_maven_plugin.simple_plugin.actions.SampleAction
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[45,37]
> cannot find symbol
> symbol : class IAction
> location: class test.pde_maven_plugin.simple_plugin.actions.SampleAction
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[45,53]
> cannot find symbol
> symbol : class ISelection
> location: class test.pde_maven_plugin.simple_plugin.actions.SampleAction
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\actions\SampleAction.java:[61,25]
> cannot find symbol
> symbol : class IWorkbenchWindow
> location: class test.pde_maven_plugin.simple_plugin.actions.SampleAction
>
>
> E:\Eclipse\workspace\PDE_Plugin_Tutorial\plugins\src\test\pde_maven_plugin\simple_plugin\Activator.java:[29,16]
> cannot find symbol
> symbol : variable super
> location: class test.pde_maven_plugin.simple_plugin.Activator
>
>
>
Re: Build number plugin drama
Yes clifton, the buildnumber plug in for me is working without mentioning
the pluginrepositories. So in case you are not using it for anything else,
you can remove it and try. Central should work, I tried before sending this
mail and it worked (fetched buildnumber-maven-plugin-1.0-beta-1 from
central).
Regards,
Amit.
On Feb 12, 2008 8:00 PM, Clifton <[EMAIL PROTECTED]> wrote:
>
> Thanx everyone! I'm going to try the version on central. Does that mean I
> just need to remove the pluginrepository section from my pom? Let me just
> give that a go and I'll ping back if I get into further trouble.
>
>
> amit kumar-18 wrote:
> >
> > This is working for me as well
> >
> >
> > org.codehaus.mojo
> > buildnumber-maven-plugin
> >
> >
> > validate
> >
> > create
> >
> >
> >
> >
> > true
> > true
> >{0,date,MM-dd-_HH.mm}
> >
> > timestamp
> >
> >
> >
> >
> >
> > What I get with this is version 1.0-beta-1, as mentioned by Nick.
> >
> > Regards,
> > Amit
> > n Feb 12, 2008 2:52 PM, <[EMAIL PROTECTED]> wrote:
> >
> >> The install page at ucalgary.ca is out of date. The buildnumber plugin
> >> has
> >> been uploaded to central and is at:
> >>
> >>
> >>org.codehaus.mojo
> >>buildnumber-maven-plugin
> >>1.0-beta-1
> >>
> >>
> >> Which version are you trying to use?
> >>
> >> Hth,
> >>
> >> Nick S.
> >>
> >>
> >> -Original Message-
> >> From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
> >> Sent: Tue 2/12/2008 10:20
> >> To: Maven Users List
> >> Subject: Re: Build number plugin drama
> >>
> >>
> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/install.html
> >>
> >> Clifton wrote:
> >> > Hi all
> >> >
> >> > My buddy and I are stumbling with the buildNumber plugin and getting
> >> nowhere
> >> > fast. We found the original version here:
> >> >
> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html
> >> > Then later stumbled across the superceding version here:
> >> > http://mojo.codehaus.org/buildnumber-maven-plugin/
> >> > Trying to use the codehaus version gives:
> >> > [INFO] The plugin 'org.codehaus.mojo:buildnumber-maven-plugin' does
> not
> >> > exist or no valid version could be found
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Build-number-plugin-drama-tp15421321s177p15434052.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Maven Concepts
Continuing on the dependency Vs dependencyManagement, I read the documents on it but after encountering the archetype:create for j2ee simple, I am not able to figure out what is the motive behind giving sub-modules of the project in the dependencyManagement section. Regards, Amit On Feb 12, 2008 7:08 PM, amit kumar <[EMAIL PROTECTED]> wrote: > Thanks Nick. I was unaware of that part. Configured the repository for > snapshots and now it is working. > > Regards, > Amit > > > On Feb 12, 2008 3:16 PM, <[EMAIL PROTECTED]> wrote: > > > How did you configure your repository? Especially take a look at the > > updatePolicy element in your snapshot repository. [1] If this one is > > omitted, it will default to "daily", so it is possible it won't take your > > newest snapshot. You can use "mvn -U" to look for newer versions of the > > snapshot dependencies. Or set the updatePolicy to another value: "The > > frequency for downloading updates - can be "always", "daily" (default), > > "interval:XXX" (in minutes) or "never" (only if it doesn't exist locally)." > > > > Hth, > > > > Nick S. > > > > [1] > > http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_snapshots > > > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Tue 2/12/2008 10:40 > > To: Maven Users List > > Subject: Re: Maven Concepts > > > > I tested with SNAPSHOT version as well. But maven still seems to prefer > > the > > local version of even the SNAPSHOT version? > > > > i have these two modules a.jar and b.jar, > > a-1.0-SNAPSHOT.jar depends on b-1.0-SNAPSHOT.jar, I tested and deployed > > b.jar at a later time stamp and again tried to build a.jar. But still it > > fetched the local version which was build at 14:29 while the one of two > > jars > > at repository is a 14:45 built? > > > > Am I missing something here? I am using the buildNumber as well to have > > the > > finalName appended with time stamp. > > > > Regards, > > Amit > > > > On Feb 8, 2008 3:52 PM, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > > > Stephen Connolly <[EMAIL PROTECTED]> schrieb: > > > > Redeploying a non-SNAPSHOT version is a _bad thing_ as Maven will > > not > > > > re-download it. > > > > > > Absolutely. Never overwrite an existing deployed file except when it > > has > > > SNAPSHOT in the version. > > > > > > Builds should be repeatable, ie you should be able to compile > > something > > > today, then compile it again next week and get the same result. This > > means > > > that stuff deployed to a repository should never change. > > > > > > The only exception is SNAPSHOT versions; when a project depends on one > > of > > > these, then it is explicitly acknowledging that repeatable builds are > > not > > > possible. > > > > > > One of the things the release plugin does is check that there are no > > > SNAPSHOT dependencies anywere; if there are then it refuses to > > continue with > > > the release process as the release is not repeatable. Of course using > > the > > > release plugin is not mandatory, but that particular check is a very > > good > > > idea. > > > > > > And because Maven assumes people never overwrite non-snapshot files, > > it > > > never bothers to check for newer ones. Only with SNAPSHOTs does maven > > look > > > for newer versions, on an "every time", "daily" or "weekly" basis as > > > configured. > > > > > > Regards, > > > Simon > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > >
maven-archetype-j2ee-simple Bug?
Hi, I have used archetype:create to create a simple J2ee Project. Though in the root pom, site is mentioned as one of the modules, but what I realised on looking up is that it doesn't gets created actually. And when you do mvn install it throws an exception telling maven is not able to find site/pom.xml ( for obvious reasons). Is this a known issue? Regards, Amit
Re: Maven Concepts
Thanks Nick. I was unaware of that part. Configured the repository for snapshots and now it is working. Regards, Amit On Feb 12, 2008 3:16 PM, <[EMAIL PROTECTED]> wrote: > How did you configure your repository? Especially take a look at the > updatePolicy element in your snapshot repository. [1] If this one is > omitted, it will default to "daily", so it is possible it won't take your > newest snapshot. You can use "mvn -U" to look for newer versions of the > snapshot dependencies. Or set the updatePolicy to another value: "The > frequency for downloading updates - can be "always", "daily" (default), > "interval:XXX" (in minutes) or "never" (only if it doesn't exist locally)." > > Hth, > > Nick S. > > [1] > http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_snapshots > > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Tue 2/12/2008 10:40 > To: Maven Users List > Subject: Re: Maven Concepts > > I tested with SNAPSHOT version as well. But maven still seems to prefer > the > local version of even the SNAPSHOT version? > > i have these two modules a.jar and b.jar, > a-1.0-SNAPSHOT.jar depends on b-1.0-SNAPSHOT.jar, I tested and deployed > b.jar at a later time stamp and again tried to build a.jar. But still it > fetched the local version which was build at 14:29 while the one of two > jars > at repository is a 14:45 built? > > Am I missing something here? I am using the buildNumber as well to have > the > finalName appended with time stamp. > > Regards, > Amit > > On Feb 8, 2008 3:52 PM, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > Stephen Connolly <[EMAIL PROTECTED]> schrieb: > > > Redeploying a non-SNAPSHOT version is a _bad thing_ as Maven will not > > > re-download it. > > > > Absolutely. Never overwrite an existing deployed file except when it has > > SNAPSHOT in the version. > > > > Builds should be repeatable, ie you should be able to compile something > > today, then compile it again next week and get the same result. This > means > > that stuff deployed to a repository should never change. > > > > The only exception is SNAPSHOT versions; when a project depends on one > of > > these, then it is explicitly acknowledging that repeatable builds are > not > > possible. > > > > One of the things the release plugin does is check that there are no > > SNAPSHOT dependencies anywere; if there are then it refuses to continue > with > > the release process as the release is not repeatable. Of course using > the > > release plugin is not mandatory, but that particular check is a very > good > > idea. > > > > And because Maven assumes people never overwrite non-snapshot files, it > > never bothers to check for newer ones. Only with SNAPSHOTs does maven > look > > for newer versions, on an "every time", "daily" or "weekly" basis as > > configured. > > > > Regards, > > Simon > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
Re: Best way to CI multi-module projects
Even with continuum I am doing the same. Adding the whole project as one( along with submodules) everything seems to work fine for me as well (by now :) ). Regards, Amit On Feb 12, 2008 7:00 PM, Milos Kleint <[EMAIL PROTECTED]> wrote: > I have the whole multimodule setup built together in one job (in hudson). > Additionally I have a separate local repository for the job.. That > turned out to work best for me.. > > Milos > > On Feb 12, 2008 2:14 PM, Chris Schmidt <[EMAIL PROTECTED]> wrote: > > I don't normally cross-post messages, but I'm not certain which list is > > the best for this question. If this breaks an etiquette rule, I > > apologize. > > > > > > > > I have a handful of maven2 multi-module projects that I have > > configured to continuously integrate within CruiseControl. Currently I > > have each submodule being built as a separate project within the CC > > configuration file. Is this the proper way to configure submodules? I > > don't want to rebuild every submodule if only one changes. However, > > I've found that breaking the modules up tends to cause many failed > > builds if I've made changes to different areas of the code base at the > > same time. > > > > > > > > For example, if I change code in a submodule within project A, and > > modify code that depends on it in project B, CC will sometimes try to > > rebuild project B first. I'm using the maven snapshot dependency plugin > > to cascade changes, but I'd really like for CC to be able to trace up > > the dependency hierarchy to know that the module in project A has > > changes as well and build it before the module in project B. > > > > > > > > Thanks, > > > > > > > > Chris Schmidt > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven xmlbeans plugin - XML-BEANS compiled schema: Incompatible minor version - expecting up to 23, got 24
I was getting the same error at Integration setup ( not at compile time). I had manually installed the 2.3.0 version of xbean and put it as dependency to the modules that required xbean.jar to compile. Or the better option as told by Basel is to specify an older version of xmlbeans plugin. Regards, Amit On Feb 11, 2008 6:38 PM, Basel Naamna <[EMAIL PROTECTED]> wrote: > > Specifying older version of xmlbeans plugin in the pom.xml file fixes the > problem. > > > Basel Naamna wrote: > > > > I'm using maven xmlbeans plugin to compile a schema, but when I run the > > project, I get: > > Caused by: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS > > compiled schema: Incompatible minor version - expecting up to 23, got 24 > > ... > > any ideas? > > > > -- > View this message in context: > http://www.nabble.com/Maven-xmlbeans-plugin---XML-BEANS-compiled-schema%3A-Incompatible-minor-version---expecting-up-to-23%2C-got-24-tp15398718s177p15411238.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Build number plugin drama
This is working for me as well
org.codehaus.mojo
buildnumber-maven-plugin
validate
create
true
true
{0,date,MM-dd-_HH.mm}
timestamp
What I get with this is version 1.0-beta-1, as mentioned by Nick.
Regards,
Amit
n Feb 12, 2008 2:52 PM, <[EMAIL PROTECTED]> wrote:
> The install page at ucalgary.ca is out of date. The buildnumber plugin has
> been uploaded to central and is at:
>
>
>org.codehaus.mojo
>buildnumber-maven-plugin
>1.0-beta-1
>
>
> Which version are you trying to use?
>
> Hth,
>
> Nick S.
>
>
> -Original Message-
> From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
> Sent: Tue 2/12/2008 10:20
> To: Maven Users List
> Subject: Re: Build number plugin drama
>
> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/install.html
>
> Clifton wrote:
> > Hi all
> >
> > My buddy and I are stumbling with the buildNumber plugin and getting
> nowhere
> > fast. We found the original version here:
> > http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html
> > Then later stumbled across the superceding version here:
> > http://mojo.codehaus.org/buildnumber-maven-plugin/
> > Trying to use the codehaus version gives:
> > [INFO] The plugin 'org.codehaus.mojo:buildnumber-maven-plugin' does not
> > exist or no valid version could be found
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
Re: Maven Concepts
I tested with SNAPSHOT version as well. But maven still seems to prefer the local version of even the SNAPSHOT version? i have these two modules a.jar and b.jar, a-1.0-SNAPSHOT.jar depends on b-1.0-SNAPSHOT.jar, I tested and deployed b.jar at a later time stamp and again tried to build a.jar. But still it fetched the local version which was build at 14:29 while the one of two jars at repository is a 14:45 built? Am I missing something here? I am using the buildNumber as well to have the finalName appended with time stamp. Regards, Amit On Feb 8, 2008 3:52 PM, Simon Kitching <[EMAIL PROTECTED]> wrote: > Stephen Connolly <[EMAIL PROTECTED]> schrieb: > > Redeploying a non-SNAPSHOT version is a _bad thing_ as Maven will not > > re-download it. > > Absolutely. Never overwrite an existing deployed file except when it has > SNAPSHOT in the version. > > Builds should be repeatable, ie you should be able to compile something > today, then compile it again next week and get the same result. This means > that stuff deployed to a repository should never change. > > The only exception is SNAPSHOT versions; when a project depends on one of > these, then it is explicitly acknowledging that repeatable builds are not > possible. > > One of the things the release plugin does is check that there are no > SNAPSHOT dependencies anywere; if there are then it refuses to continue with > the release process as the release is not repeatable. Of course using the > release plugin is not mandatory, but that particular check is a very good > idea. > > And because Maven assumes people never overwrite non-snapshot files, it > never bothers to check for newer ones. Only with SNAPSHOTs does maven look > for newer versions, on an "every time", "daily" or "weekly" basis as > configured. > > Regards, > Simon > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: PDE Plugin
like Plug in dependencies, which the maven is not able to comprehend. I have tried the plug in long back, but faced same error. Then had to drop it for a while. Could someone please help me out, who knows the workaround of the solution for the problem. If I am not wrong, in one line pde plugin is not able to handle the plug in dependencies for the project. Thanks in anticipation. Regards, Amit On 2/12/08, amit kumar <[EMAIL PROTECTED]> wrote: > Hi, > Could anyone please help on a good document(blog/tutorial/article) on > PDE plug in, I followed http://mojo.codehaus.org/pde-maven-plugin/ but > could not able to mavenize an already existing plug in project. > > Regards, > Amit > > On 1/4/08, amit kumar <[EMAIL PROTECTED]> wrote: > > But I doubt for any jar unavailable, because I am downloading the jars > from > > central repository. > > I will email the pom.xml and stack trace. > > > > > > On Jan 4, 2008 6:56 PM, Vikramaditya Garg <[EMAIL PROTECTED]> > > wrote: > > > > > > > > Please sent the exceptions and error what you are getting.Probable > reason > > > include that u may not be having some jar in your local repo which may > be > > > cause of the concern. > > > > > > Also check ur proxy settings... > > > > > > Thanks > > > Vikramaditya Garg > > > Technical Specialist > > > BCM-ADGE > > > Infosys Technologies Ltd. > > > > > > -Original Message- > > > From: amit kumar [mailto:[EMAIL PROTECTED] > > > Sent: Friday, January 04, 2008 6:52 PM > > > To: Maven Users List > > > Subject: PDE Plugin > > > > > > Has anyone successfully worked out with maven-pde-plugin for eclipse. > This > > > is this eclipse plug in project that i have been trying to build. But > > > maven > > > is not able to resolve the plug in dependencies ( the one defined in > > > eclipse). i am trying to build it from command line. > > > I followed the tutorial on codehaus but it did not work. > > > > > > Link I have been following http://mojo.codehaus.org/pde-maven-plugin/ > > > > > > > > > Regards, > > > Amit > > > > > > CAUTION - Disclaimer * > > > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended > > > solely for the use of the addressee(s). If you are not the intended > > > recipient, please notify the sender by e-mail and delete the original > > > message. Further, you are not to copy, disclose, or distribute this > e-mail > > > or its contents to any other person and any such actions are unlawful. > > This > > > e-mail may contain viruses. Infosys has taken every reasonable > precaution > > to > > > minimize this risk, but is not liable for any damage you may sustain as > a > > > result of any virus in this e-mail. You should carry out your own virus > > > checks before opening the e-mail or attachment. Infosys reserves the > right > > > to monitor and review the content of all messages sent to or from this > > > e-mail address. Messages sent to or from this e-mail address may be > stored > > > on the Infosys e-mail system. > > > ***INFOSYS End of Disclaimer INFOSYS*** > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PDE Plugin
Hi, Could anyone please help on a good document(blog/tutorial/article) on PDE plug in, I followed http://mojo.codehaus.org/pde-maven-plugin/ but could not able to mavenize an already existing plug in project. Regards, Amit On 1/4/08, amit kumar <[EMAIL PROTECTED]> wrote: > But I doubt for any jar unavailable, because I am downloading the jars from > central repository. > I will email the pom.xml and stack trace. > > > On Jan 4, 2008 6:56 PM, Vikramaditya Garg <[EMAIL PROTECTED]> > wrote: > > > > > Please sent the exceptions and error what you are getting.Probable reason > > include that u may not be having some jar in your local repo which may be > > cause of the concern. > > > > Also check ur proxy settings... > > > > Thanks > > Vikramaditya Garg > > Technical Specialist > > BCM-ADGE > > Infosys Technologies Ltd. > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 04, 2008 6:52 PM > > To: Maven Users List > > Subject: PDE Plugin > > > > Has anyone successfully worked out with maven-pde-plugin for eclipse. This > > is this eclipse plug in project that i have been trying to build. But > > maven > > is not able to resolve the plug in dependencies ( the one defined in > > eclipse). i am trying to build it from command line. > > I followed the tutorial on codehaus but it did not work. > > > > Link I have been following http://mojo.codehaus.org/pde-maven-plugin/ > > > > > > Regards, > > Amit > > > > CAUTION - Disclaimer * > > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended > > solely for the use of the addressee(s). If you are not the intended > > recipient, please notify the sender by e-mail and delete the original > > message. Further, you are not to copy, disclose, or distribute this e-mail > > or its contents to any other person and any such actions are unlawful. > This > > e-mail may contain viruses. Infosys has taken every reasonable precaution > to > > minimize this risk, but is not liable for any damage you may sustain as a > > result of any virus in this e-mail. You should carry out your own virus > > checks before opening the e-mail or attachment. Infosys reserves the right > > to monitor and review the content of all messages sent to or from this > > e-mail address. Messages sent to or from this e-mail address may be stored > > on the Infosys e-mail system. > > ***INFOSYS End of Disclaimer INFOSYS*** > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Concepts
what is the difference between dependency and dependencyManagement? I mean when do we use dependency and when do we use dependencyManagement? On Feb 8, 2008 10:26 PM, amit kumar <[EMAIL PROTECTED]> wrote: > That makes two of us Dhruva. Seriously guys thanks a lot. Great help. > > > On Feb 8, 2008 9:46 PM, Dhruva Reddy <[EMAIL PROTECTED]> wrote: > > > This really clears things up--many thanks! > > > > > > -- > > Dhruva B. Reddy > > Senior Associate of Technology, Level 2 | Sapient > > > > 25 1st Street > > Cambridge, MA, 02141, USA > > desk: +1 617 452 1900 > > fax: +1 617 621 1300 > > > > www.sapient.com > > > > -Original Message- > > From: John Casey [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 07 February 2008 17:01 > > To: Maven Users List > > Subject: Re: Maven Concepts > > > > You've got it exactly right. > > > > Maven builds are usually oriented around the concept of a lifecycle, > > which consists of phases in a specific order. Each phase has zero or > > more mojos (usually called goals) bound to it. Each phase in the > > lifecycle implies all of the phases that come before it. This allows > > users to bind (or configure) different goals to different phases of > > the build, then the standard phase names to run the build. The > > default goals for a given type of project are also bound to the > > lifecycle in this way, but behind the scenes, such that the user can > > supplement these default goals using configurations in the pom.xml. > > > > So, if you have a jar project (jar), you might > > have something like this: > > > > Phase Goals > > --- > > > > validate(none) > > initialize (none) > > ... > > compileorg.apache.maven.plugins:maven-compiler- > > plugin:compile > > ... > > testorg.apache.maven.plugins:maven-surefire- > > plugin:test > > ... > > package org.apache.maven.plugins:maven-jar-plugin:jar > > ... > > install org.apache.maven.plugins:maven-install- > > plugin:install > > ... > > etc. > > > > Now, if you just want to compile your project, you simply call the > > 'compile' phase, like this: > > > > mvn compile > > > > If you want to run the unit tests, call this: > > > > mvn test > > > > Note that in order to run unit tests, you must have compiled your > > project's main sources. That's handled here, since the test phase is > > later in the lifecycle than the compile phase...'test' implies > > 'compile' and all the other phases (in order) that come before 'test'. > > > > On the other hand, Maven also supports certain one-off goals that are > > usually meant to help manage the project build in certain special > > cases, or give information about the build. One such example gives > > you a glimpse of the POM after all inheritance and profile injection > > has been completed: > > > > mvn help:effective-pom > > > > which is shorthand for: > > > > mvn org.apache.maven.plugins:maven-help-plugin:effective-pom > > > > > > Hope that helps, > > > > -john > > > > On Feb 7, 2008, at 4:50 PM, Dhruva Reddy wrote: > > > > > I know this seems like a silly thing to post on here, but... > > > > > > What exactly is a goal and what is a phase? I can't find a good > > > answer in the documentation and there's a lot of seemingly > > > conflicting information out there. > > > > > > My current understanding is that a phase is a part of a lifecycle > > > (process-resources, compile, etc). A goal is somewhat analogous to > > > an ANT-task, but with a focus on what should happen, rather than > > > how it is done. > > > > > > Can someone clear this up for me, giving examples? > > > > > > Thanks, > > > Dhruva > > > > --- > > John Casey > > Committer and PMC Member, Apache Maven > > mail: jdcasey at commonjava dot org > > blog: http://www.ejlife.net/blogs/john > > rss: http://feeds.feedburner.com/ejlife/john > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: Maven Concepts
That makes two of us Dhruva. Seriously guys thanks a lot. Great help. On Feb 8, 2008 9:46 PM, Dhruva Reddy <[EMAIL PROTECTED]> wrote: > This really clears things up--many thanks! > > > -- > Dhruva B. Reddy > Senior Associate of Technology, Level 2 | Sapient > > 25 1st Street > Cambridge, MA, 02141, USA > desk: +1 617 452 1900 > fax: +1 617 621 1300 > > www.sapient.com > > -Original Message- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: Thursday, 07 February 2008 17:01 > To: Maven Users List > Subject: Re: Maven Concepts > > You've got it exactly right. > > Maven builds are usually oriented around the concept of a lifecycle, > which consists of phases in a specific order. Each phase has zero or > more mojos (usually called goals) bound to it. Each phase in the > lifecycle implies all of the phases that come before it. This allows > users to bind (or configure) different goals to different phases of > the build, then the standard phase names to run the build. The > default goals for a given type of project are also bound to the > lifecycle in this way, but behind the scenes, such that the user can > supplement these default goals using configurations in the pom.xml. > > So, if you have a jar project (jar), you might > have something like this: > > Phase Goals > --- > > validate(none) > initialize (none) > ... > compileorg.apache.maven.plugins:maven-compiler- > plugin:compile > ... > testorg.apache.maven.plugins:maven-surefire- > plugin:test > ... > package org.apache.maven.plugins:maven-jar-plugin:jar > ... > install org.apache.maven.plugins:maven-install- > plugin:install > ... > etc. > > Now, if you just want to compile your project, you simply call the > 'compile' phase, like this: > > mvn compile > > If you want to run the unit tests, call this: > > mvn test > > Note that in order to run unit tests, you must have compiled your > project's main sources. That's handled here, since the test phase is > later in the lifecycle than the compile phase...'test' implies > 'compile' and all the other phases (in order) that come before 'test'. > > On the other hand, Maven also supports certain one-off goals that are > usually meant to help manage the project build in certain special > cases, or give information about the build. One such example gives > you a glimpse of the POM after all inheritance and profile injection > has been completed: > > mvn help:effective-pom > > which is shorthand for: > > mvn org.apache.maven.plugins:maven-help-plugin:effective-pom > > > Hope that helps, > > -john > > On Feb 7, 2008, at 4:50 PM, Dhruva Reddy wrote: > > > I know this seems like a silly thing to post on here, but... > > > > What exactly is a goal and what is a phase? I can't find a good > > answer in the documentation and there's a lot of seemingly > > conflicting information out there. > > > > My current understanding is that a phase is a part of a lifecycle > > (process-resources, compile, etc). A goal is somewhat analogous to > > an ANT-task, but with a focus on what should happen, rather than > > how it is done. > > > > Can someone clear this up for me, giving examples? > > > > Thanks, > > Dhruva > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven Concepts
Continuing on this thread I would also like to put a doubt(misconception)- Until yesterday I used to think that if I have an artifact on local repository + remote repository with same groupId-artifactId-version. The maven will take the one which is built at a later time or some system property attached to it which maven uses to differentiate. The origin for this assumption was no matter if the artifact is present in my local repository maven shows Downloading \\remoteRepository\org\apache\x\x-1.0.pom Downloading http:\\repo1.maven.org\org\apache\x\x-1.0.pom . . . . . What I assumed of this was that it compares where the latest of the artifact is available even with same groupId+artifactId+version. But yesterday when I cross checked even at the remote repository had a artifact newly deployed (though with same groupId+artifactId+versionId) what I was seeing in the classpath was the one from local repository. Am I right in what I am concluding? Or again missing somewhere. If what I have concluded upon is right, is there a way to make maven pick up the one from remote repository(in case it is build and deployed later? ) Thanks and regards, Amit On Feb 8, 2008 4:55 AM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Dhruva Reddy wrote: > > > What exactly is a goal and what is a phase? > > In maven 1, there were only goals, and goals were specific targets that > were embedded in specific maven plugins, a bit like an ant target. > > So the jar plugin would have the jar goal which when run, would jar up > some classes. > > It soon became apparent that this leaves too much up to the end user: > what if the artifact you are producing isn't a jar, but an ear instead? > Or a war file? Why should the user have to know or care that they must > run the ear:ear goal instead of the jar:jar goal? > > Enter the phases of the lifecycle in maven 2. > > Plugins attach various goals to the various phases in the lifecycles, > and depending on which phase of the lifecycle you've asked maven to > complete, all the relevant goals attached to that lifecycle will be run > up to that phase. > > So if you run "mvn install" (or "run all goals in all phases up until > the 'install' phase"), maven figures out for itself that the > compile:compile goal must run, and the ear:ear goal (because the > artifact is an ear file), the user no longer needs to care. > > So to sum up: > > The lifecycle contains a list of phases, and each phase has a goal or > goals attached to that phase. So running a phase is a convenient way of > saying "run all goals I need to run to make this artifact up to this > phase, and don't tell me what those goals are, I don't care". > > Regards, > Graham > -- >
Conceptual Confusion about build and release process using maven.
Hi, Please pardon me for such a long mail but couldn't cut it any shorter. After 2 months of being assigned the task of mavenizing the whole product at my workplace and build and release automation process with Continuous Integration, I have been able to mavenize the product and put continuum and mavenized CVS structure in sync. But while pondering over how to go about with the build an release strategy I got myself in deep confusion. The product (as usual) has several submodules with separate developers and with many intermodule dependencies. My understanding of the whole process till now has been like below Development environment, after intranet maven repository in place would be something like this: owner of module A would deploy the A.jar on maven repository from where the other module owners which depend on a.jar would fetch it from. And as the development goes on for module A, the owner of module will keep on changing the versions (with in an iteration as well) and deploying it on to the maven repository and dependent modules will keep on changing the version in their pom.xml for "a.jar".(unsure about whether this is how it happens) All these developments in various modules keep on getting committed into the CVS from where the Continuum keeps on checking out and building ( Continuous Integration). Now my confusion over my own understanding and assumption is: 1) During the development process within an iteration, how to make sure that all the module owners dependent on "a.jar" keeps up to date with the changing versions of a.jar as the development goes on until Integration Testing. 2) If a module owner dependent on a.jar fails to update the version of the a.jar in the pom.xml and/or miss to commit the updated pom.xml with a contemporary version of a.jar. Continuous Integration at Continuum would suffer( assuming that even with not up to date version of a.jar the module still gets through build), Pardon me for any wrong assumptions, I do not have much exposure to the process. Regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problematic Parent tag.
But under the parent of a.jar there are other projects as well which are owned by different developers. The scenario is like: *Parent Project a.jar*(developer1)* c.war*(developer2)* d.jar*(developer3) All the three developers are responsible for deploying artifacts. So how to ensure the Parent Project's pom gets gets installed/deployed in the Intranet repository, and who should be installing that? Because every developer does like *C:\Parent Project\a>mvn deploy. *This doesn't result in the deployment of parent project's pom. Thanks and Regards, Amit On Feb 5, 2008 7:20 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > amit kumar wrote: > > > Say I have deployed *a.jar* ( whose pom has a parent tag, since it is a > > sub-module of the whole project as such), and *b.jar* has *a.jar* in its > > dependency. > > Now when I run a maven goal I see the error in which it tells that maven > was > > not able to find the the parent pom ( it sees the parent tag in the * > a.jar's > > * pom and tries to look for it, which obviously it doesn't find.) The > parent > > to *a.jar* is just a logical project with packaging type as pom. > > > > Could someone please help out. This problem kind of brought everything > in > > release automation on the knees. > > You need to install and/or deploy and release the parent pom as well as > your a.jar and b.jar, and you need to install it first. > > If you do a deploy or an install from the parent parent project, maven > figures out how to do this on its own. > > Parent pom files go into both local and remote repositories, just like > the pom files belonging to the jars, and follow the same rules. > > Regards, > Graham > -- >
Problematic Parent tag.
Hi, It is supposed to deploy company artifacts to the LAN repository and use them from other artifacts which depend on them. But I am facing this problem with the parent tag inside the pom of the deployed artifact. Say I have deployed *a.jar* ( whose pom has a parent tag, since it is a sub-module of the whole project as such), and *b.jar* has *a.jar* in its dependency. Now when I run a maven goal I see the error in which it tells that maven was not able to find the the parent pom ( it sees the parent tag in the *a.jar's * pom and tries to look for it, which obviously it doesn't find.) The parent to *a.jar* is just a logical project with packaging type as pom. Could someone please help out. This problem kind of brought everything in release automation on the knees. Regards, Amit
Re: Avoid version number in the build
Thanks. We would be sticking to version numbers in the build names. Regards, Amit On Feb 5, 2008 3:39 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > amit kumar wrote: > > > How can I avoid version number in the build name and put it in Manifest > > file.? > > Which one is considered a better procedure? > > Stripping version numbers causes all sorts of problems, and isn't > recommended at all. Maven uses the version numbers heavily to make sure > code can depend on the right dependencies, and without them, you would > have no way to change or upgrade your code. > > Regards, > Graham > -- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Avoid version number in the build
Hi, How can I avoid version number in the build name and put it in Manifest file.? Which one is considered a better procedure? Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build profiles
Thank you so much Allen. Been a great help.
is not listed among them, but it is working for a single
project that I tried to use different profiles. I would try with your
suggestions and would let you know.
Thanks and regards,
Amit
On Feb 5, 2008 2:11 AM, Allen, Daniel <[EMAIL PROTECTED]> wrote:
> Heh. I should take my own advice--when I was reviewing the profiles
> intro I linked you to, it says:
>
> Profiles in pom.xml
>
> On the other hand, if your profiles can be reasonably specified inside
> the POM, you have many more options. The trade-off, of course, is that
> you can only modify that project and it's sub-modules. Since these
> profiles are specified inline, and therefore have a better chance of
> preserving portability, it's reasonable to say you can add more
> information to them without the risk of that information being
> unavailable to other users.
>
> Profiles specified in the POM can modify the following POM elements:
>
> *
> *
> *
> *
> * (not actually available in the main POM, but used
> behind the scenes)
> *
> *
> *
> *
> --->* a subset of the element, which consists of:
> o
> o
> o
> o
>
>
> Note that isn't listed among those. So, while I still think
> you should have more than just the one profile to avoid confusing
> defaults and precedences, one thing you'll have to do is put the
> directory name into a and then in your pom.xml files, have
>
>
> ${whatever.you.called.the.directory.property}
> .
> .
> .
>
>
> ~DVA
>
> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
>
> Sent: Monday, February 04, 2008 3:18 PM
> To: Maven Users List
> Subject: Re: build profiles
>
> Actually the current setup is the most basic I guess. I was just
> trying to separate development environment(destination directory for
> the sub modules) an integration environment( the profile I want to use
> to specify a location which would get inherited by every sub module so
> that all of them could be at one place.)
>
> For sub modules I am define like.
>
>
> C:\Final
>
>
>
> For parent project(parent of all) I am defining a profile( i think I
> would have to, to achieve this separation) which would be used when
> build would be triggered at the time ot Continuous Integration. I am
> not defining anything else in this profile besides the destination
> directory.
>
>
>
> int
>
> C:\Diff
>
>
>
>
>
> something like mvn -P int
>
>
> Amit
>
>
> On Feb 4, 2008 1:47 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote:
> > So... you're saying that your (profile1, according to your
> > example command-line call below) is defined in/for the parent POM?
> >
> > I think I'm not 100% understanding your setup. Could you give me a
> more
> > detailed explanation of what profiles and properties you have defined,
> > where those are, and which ones you do and don't want active? In fact,
> > if you have some web space somewhere, maybe you could just upload your
> > POMs and link to them?
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Monday, February 04, 2008 2:33 PM
> > To: Maven Users List
> >
> > Subject: Re: build profiles
> >
> > Currently i am not using any profile(tag) for sub modules, I am just
> > mentioning tag inside tag. Do i need to have
> > separate profile to do that?
> >
> > regards,
> > Amit
> >
> > On Feb 4, 2008 1:03 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote:
> > > When I was doing profiles for the first time, I noticed that
> anything
> > I
> > > put in profiles.xml was active by default, and that my dev profile
> > > overrode my live release profile. This may be your problem. Try
> > adding:
> > >
> > >
> > > false
> > >
> > >
> > > to the dev profile that is currently overriding the other. In fact,
> > this
> > > may or may not be regarded by the community as a "best practice,"
> (I'm
> > > new at Maven too), but for a project where only one profile should
> > ever
> > > be active at a time, I add those lines to all the profiles, and then
> > > just explicitly call the one I want at the command line with '-P
> > > profile_name'.
> > >
> > > Hope that helps.
> > > ~Dan Allen
> > >
> > >
> &g
Re: build profiles
Actually the current setup is the most basic I guess. I was just trying to separate development environment(destination directory for the sub modules) an integration environment( the profile I want to use to specify a location which would get inherited by every sub module so that all of them could be at one place.) For sub modules I am define like. C:\Final For parent project(parent of all) I am defining a profile( i think I would have to, to achieve this separation) which would be used when build would be triggered at the time ot Continuous Integration. I am not defining anything else in this profile besides the destination directory. int C:\Diff something like mvn -P int Amit On Feb 4, 2008 1:47 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote: > So... you're saying that your (profile1, according to your > example command-line call below) is defined in/for the parent POM? > > I think I'm not 100% understanding your setup. Could you give me a more > detailed explanation of what profiles and properties you have defined, > where those are, and which ones you do and don't want active? In fact, > if you have some web space somewhere, maybe you could just upload your > POMs and link to them? > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 04, 2008 2:33 PM > To: Maven Users List > > Subject: Re: build profiles > > Currently i am not using any profile(tag) for sub modules, I am just > mentioning tag inside tag. Do i need to have > separate profile to do that? > > regards, > Amit > > On Feb 4, 2008 1:03 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote: > > When I was doing profiles for the first time, I noticed that anything > I > > put in profiles.xml was active by default, and that my dev profile > > overrode my live release profile. This may be your problem. Try > adding: > > > > > > false > > > > > > to the dev profile that is currently overriding the other. In fact, > this > > may or may not be regarded by the community as a "best practice," (I'm > > new at Maven too), but for a project where only one profile should > ever > > be active at a time, I add those lines to all the profiles, and then > > just explicitly call the one I want at the command line with '-P > > profile_name'. > > > > Hope that helps. > > ~Dan Allen > > > > > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 04, 2008 1:58 PM > > To: Maven Users List > > Subject: build profiles > > > > Hi, > > I am trying to have different build profiles for my development > > environment and integration environment. All I want is to have > > different destination directories. My project has sub-modules and at > > the time of Integration when I run the maven build for the parent > > project, the destination directory that I want at the integration > > environment gets overridden by the sub module directory tag. > > > > I have tried something like this. > > > > ParentProject > >-pom.xmlhave a profile with destination > > directory say C:\final > > > >-Child1destination directory in the > > build tag D:\dev > > > >-Child2 > > > > > > When I run mvn install -P profile1. The C:\final gets overridden by > > D:\dev. > > > > How shall I go about it? > > > > > > regards, > > Amit > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > > This message may contain confidential, proprietary, or legally > privileged information. No confidentiality or privilege is waived by any > transmission to an unintended recipient. If you are not an intended > recipient, please notify the sender and delete this message immediately. > Any views expressed in this message are those of the sender, not those > of any entity within the KBC Financial Products group of companies > (together referred to as "KBC FP"). > > > > This message does not create any obligation, contractual or otherwise, > on the part of KBC FP. It is not an offer (or solicitation of an offer) > of, or a recommendation to buy or sell, any financial product. Any > prices or other values included in this message are indicative only, and > do no
Re: build profiles
Currently i am not using any profile(tag) for sub modules, I am just mentioning tag inside tag. Do i need to have separate profile to do that? regards, Amit On Feb 4, 2008 1:03 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote: > When I was doing profiles for the first time, I noticed that anything I > put in profiles.xml was active by default, and that my dev profile > overrode my live release profile. This may be your problem. Try adding: > > > false > > > to the dev profile that is currently overriding the other. In fact, this > may or may not be regarded by the community as a "best practice," (I'm > new at Maven too), but for a project where only one profile should ever > be active at a time, I add those lines to all the profiles, and then > just explicitly call the one I want at the command line with '-P > profile_name'. > > Hope that helps. > ~Dan Allen > > > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 04, 2008 1:58 PM > To: Maven Users List > Subject: build profiles > > Hi, > I am trying to have different build profiles for my development > environment and integration environment. All I want is to have > different destination directories. My project has sub-modules and at > the time of Integration when I run the maven build for the parent > project, the destination directory that I want at the integration > environment gets overridden by the sub module directory tag. > > I have tried something like this. > > ParentProject >-pom.xmlhave a profile with destination > directory say C:\final > >-Child1destination directory in the > build tag D:\dev > >-Child2 > > > When I run mvn install -P profile1. The C:\final gets overridden by > D:\dev. > > How shall I go about it? > > > regards, > Amit > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- > This message may contain confidential, proprietary, or legally privileged > information. No confidentiality or privilege is waived by any transmission to > an unintended recipient. If you are not an intended recipient, please notify > the sender and delete this message immediately. Any views expressed in this > message are those of the sender, not those of any entity within the KBC > Financial Products group of companies (together referred to as "KBC FP"). > > This message does not create any obligation, contractual or otherwise, on the > part of KBC FP. It is not an offer (or solicitation of an offer) of, or a > recommendation to buy or sell, any financial product. Any prices or other > values included in this message are indicative only, and do not necessarily > represent current market prices, prices at which KBC FP would enter into a > transaction, or prices at which similar transactions may be carried on KBC > FP's own books. The information contained in this message is provided "as > is", without representations or warranties, express or implied, of any kind. > Past performance is not indicative of future returns. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build profiles
Hi, I am trying to have different build profiles for my development environment and integration environment. All I want is to have different destination directories. My project has sub-modules and at the time of Integration when I run the maven build for the parent project, the destination directory that I want at the integration environment gets overridden by the sub module directory tag. I have tried something like this. ParentProject -pom.xmlhave a profile with destination directory say C:\final -Child1destination directory in the build tag D:\dev -Child2 When I run mvn install -P profile1. The C:\final gets overridden by D:\dev. How shall I go about it? regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: .m2/settings.xml
Okay. actually that's the file I copied into .m2 folder thinking as of a temporary workaround.(now realise this is how it should be). Thanks. On Feb 4, 2008 12:22 PM, Allen, Daniel <[EMAIL PROTECTED]> wrote: > There's also a sample settings.xml file in the directory that Maven > installs to, under the /conf subdirectory. It contains pretty much > everything you might need to put into your settings, in commented-out > generic form. > > ~Dan Allen > > > -----Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 04, 2008 1:00 PM > To: Maven Users List > Subject: .m2/settings.xml > > Hi, > where is .m2/settings.xml? I saw this first in the maven plugin for > eclipse. It keeps looking for %USER_HOME%/.m2/settings.xml. But I can > not find this file inside the .m2 folder. Do I have to create it > manually? Or it is supposed to be generated at the time of .m2 folder > gets created. > > Amit > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- > This message may contain confidential, proprietary, or legally privileged > information. No confidentiality or privilege is waived by any transmission to > an unintended recipient. If you are not an intended recipient, please notify > the sender and delete this message immediately. Any views expressed in this > message are those of the sender, not those of any entity within the KBC > Financial Products group of companies (together referred to as "KBC FP"). > > This message does not create any obligation, contractual or otherwise, on the > part of KBC FP. It is not an offer (or solicitation of an offer) of, or a > recommendation to buy or sell, any financial product. Any prices or other > values included in this message are indicative only, and do not necessarily > represent current market prices, prices at which KBC FP would enter into a > transaction, or prices at which similar transactions may be carried on KBC > FP's own books. The information contained in this message is provided "as > is", without representations or warranties, express or implied, of any kind. > Past performance is not indicative of future returns. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: .m2/settings.xml
Thanks a ton! On Feb 4, 2008 12:17 PM, Tomasz Pik <[EMAIL PROTECTED]> wrote: > > On Feb 4, 2008 7:00 PM, amit kumar <[EMAIL PROTECTED]> wrote: > > Hi, > > where is .m2/settings.xml? I saw this first in the maven plugin for > > eclipse. It keeps looking for %USER_HOME%/.m2/settings.xml. But I can > > not find this file inside the .m2 folder. Do I have to create it > > manually? Or it is supposed to be generated at the time of .m2 folder > > gets created. > > You need to create it manually. > This may also help: http://maven.apache.org/settings.html > > Regards, > Tomek > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.m2/settings.xml
Hi, where is .m2/settings.xml? I saw this first in the maven plugin for eclipse. It keeps looking for %USER_HOME%/.m2/settings.xml. But I can not find this file inside the .m2 folder. Do I have to create it manually? Or it is supposed to be generated at the time of .m2 folder gets created. Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven renaming jar files
Actually all that happened ( installing commons into the LAN repository ) on the second day of i started using maven(2nd week of my first job :) ), there has been a strict deadline for that. But anyways I guess these are just lame excuses for misusing maven(unintentional), but at that time thats' what I thought it is like(which could be wrong). And my experience with groupId's has always been confusing, at places it is the package name while others artifactId and groupId becomes the same. That amplified the motivation to commit the mistake, and there are few commons artifacts being used here at my workplace which are not there in the repo1.maven.org ( i.e. commons-email-1.0-mod.jar). But I believe everyone learns with time, and learning is best when it comes from the mistakes you commit. Thanks for the help. Regards, Amit On Jan 31, 2008 1:57 PM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > Or if you are checking them in manually, at least use a different version > which includes your company name, e.g. > > commons-logging > commins-logging > 1.0-mycompany-1 > > That way maven will at least detect that these are different versions of the > same artifact and the version ranges and preferences should* let you pick > your one! > > -Stephen > > * Yes I know some people have issues with version ranges, etc. but there are > ways of making them work, or at least using a dependencyManagement section > > > On Jan 31, 2008 4:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > We've had more than one person show up on this list complaining about > > strange difficulties with Maven. After a bit of prodding, they tell us > > that they manually created their repo and the pom files, if they exist > > at all, are just GAV with no transitive deps. And then they're usually > > complaining about how Maven isn't working like they expected. > > > > I just want to make sure this happens to as few people as possible. If > > you know what you're doing and want to check-in some files, please do > > it, especially for things like Websphere and Weblogic that will never > > appear in the Central repo. > > > > But doing this for things like commons-* is a bad practice. Even if > > you know what you're doing, you probably should not be checking in > > files like these manually. > > > > Wayne > > > > On 1/31/08, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > I've certainly done something similar in the past. To reduce network > > traffic, and to better control what libs are used, it is nice to have a > > repository on a local server hosting the jars you need. > > > > > > It is very tempting to just take the set of jars you have always been > > using (in an existing ant-based build process or similar) and just upload > > them to that new repository. It is certainly easier than finding a maven > > repository proxy application, and setting that up. > > > > > > I don't see a lot wrong with doing that - except that you do need to get > > the group ids right! > > > > > > Of course long-term, having a proper repository manager installed > > locally appears to be the right solution. Some day I have to get that > > organised for my workplace... > > > > > > Interesting to see that the war plugin does detect filename clashes; as > > discussed in another thread recently it appears that the dependency plugin > > does not... > > > > > > Regards, > > > Simon > > > > > > Wayne Fay <[EMAIL PROTECTED]> schrieb: > > > > If you're using "mvn install" or "mvn deploy" to install/deploy common > > > > artifacts like commons-logging etc, then you're probably using Maven > > > > wrong. > > > > > > > > What you've described is exactly what the problem was. You had added > > > > c-l as a particular G/A/V and then c-l was coming in as a transitive > > > > dep under a different G/A/V. Since the plugin detected a name > > > > collision, it expanded the name to include the group as well, to make > > > > it unique. > > > > > > > > Why did you install/deploy commons-logging instead of simply adding a > > > > ? You're not the first person to report doing this, so I > > > > want to understand if there is a failure in the documentation > > > > somewhere or if new users are simply making poor assumptions about > > > > what Maven does. > > > > > > > > Wayne > > > > > > > > On 1/31
Re: Dependency resolution of maven-war-plugin
regexp-1.3.jar was getting packaged with the final war. as a dependency of buildnumber plugin On Jan 31, 2008 4:40 PM, amit kumar <[EMAIL PROTECTED]> wrote: > maven-war-plugin's 2.1-alpha-1 version. > and maven 2.0.7 > > One of the buildnumber-maven-plugin's dependency was getting packaged > unless I put it explicitly and made it available at compile time. > > > On Jan 31, 2008 4:33 PM, <[EMAIL PROTECTED]> wrote: > > This is the first time I see that a plugin transitive dependency makes it > > into the final artifact. What versions of maven and the maven-war-plugin > > are you using? > > > > With regards, > > > > Nick Stolwijk > > > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Thu 1/31/2008 11:56 AM > > To: Maven Users List > > Subject: Re: Dependency resolution of maven-war-plugin > > > > Yes Felix maven-war-plugin does include the transitive dependencies. > > For a transitive dependency of a plugin, the way(workaround) I found > > and using is to declare that dependency explicitly in your pom.xml and > > declare it to be available at only compile time ( tag). > > > > For the transitive dependencies of the rest of the dependencies I am > > using tag with in the dependency tag. That probably be not > > the sanest way of it, but this was what I could find out with the help > > of other maven users here on the list. > > > > Amit > > > > On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote: > > > Hello > > > > > > I have a question re dependency resolution of the maven-war-plugin. > > > If I run 'mvn install' a war is built including the library xbeans.jar > > > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this > > > dependency included though not declared? > > > > > > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns > > > with no result. It seems to me that maven-war-plugin includes also > > > transitive plugin dependencies. > > > > > > Thanks for your help, Felix > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency resolution of maven-war-plugin
maven-war-plugin's 2.1-alpha-1 version. and maven 2.0.7 One of the buildnumber-maven-plugin's dependency was getting packaged unless I put it explicitly and made it available at compile time. On Jan 31, 2008 4:33 PM, <[EMAIL PROTECTED]> wrote: > This is the first time I see that a plugin transitive dependency makes it > into the final artifact. What versions of maven and the maven-war-plugin are > you using? > > With regards, > > Nick Stolwijk > > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Thu 1/31/2008 11:56 AM > To: Maven Users List > Subject: Re: Dependency resolution of maven-war-plugin > > Yes Felix maven-war-plugin does include the transitive dependencies. > For a transitive dependency of a plugin, the way(workaround) I found > and using is to declare that dependency explicitly in your pom.xml and > declare it to be available at only compile time ( tag). > > For the transitive dependencies of the rest of the dependencies I am > using tag with in the dependency tag. That probably be not > the sanest way of it, but this was what I could find out with the help > of other maven users here on the list. > > Amit > > On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote: > > Hello > > > > I have a question re dependency resolution of the maven-war-plugin. > > If I run 'mvn install' a war is built including the library xbeans.jar > > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this > > dependency included though not declared? > > > > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns > > with no result. It seems to me that maven-war-plugin includes also > > transitive plugin dependencies. > > > > Thanks for your help, Felix > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency resolution of maven-war-plugin
Yes Felix maven-war-plugin does include the transitive dependencies. For a transitive dependency of a plugin, the way(workaround) I found and using is to declare that dependency explicitly in your pom.xml and declare it to be available at only compile time ( tag). For the transitive dependencies of the rest of the dependencies I am using tag with in the dependency tag. That probably be not the sanest way of it, but this was what I could find out with the help of other maven users here on the list. Amit On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote: > Hello > > I have a question re dependency resolution of the maven-war-plugin. > If I run 'mvn install' a war is built including the library xbeans.jar > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this > dependency included though not declared? > > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns > with no result. It seems to me that maven-war-plugin includes also > transitive plugin dependencies. > > Thanks for your help, Felix > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven renaming jar files
I have overcome the problem. And guess know the reason for that, actually at the time of creating the LAN maven repository, I have installed common components under org.apache.commons groupId ( assuming the convention of groupId as package name ). So now when I was including commons-logging as dependency in my pom.xml, what I added to pom looked like org.apache.commons commons-logging 1.1 But there was another dependency in my pom.xml which as commons-logging as transitive dependency with same version, so what was happening(probably) was that maven instead of overriding the jar file was renaming it, may be because the jars were differently identified as groupId+artifactId+version. Still a little confused about my own explanation of the happenings :) Amit On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > Looks weird. > Do you use a released version ? or the current snapshot ? > > Could you load an issue in jira with a simple project which reproduce this ? > > -- > Olivier > > 2008/1/30, amit kumar <[EMAIL PROTECTED]>: > > > Hi,. > > When I am packaging a WAR project, I am seeing the following thing > > happening... > > > > [DEBUG] Processing: commons-logging-1.1.jar > > [DEBUG] Duplicate found: commons-logging-1.1.jar > > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar > > > > Any idea why this happens and how to avoid this? > > I am mentioning commons-logging-1.1 as my dependency in the pom.xml, > > and have suppressed the other versions of commons logging which were > > getting packaged as transitive dependencies of project dependencies > > using tag in dependency taf. Same is happening with > > commons-digester and other dependencies. > > > > > > Regards, > > Amit > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven renaming jar files
Hi,. When I am packaging a WAR project, I am seeing the following thing happening... [DEBUG] Processing: commons-logging-1.1.jar [DEBUG] Duplicate found: commons-logging-1.1.jar [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar Any idea why this happens and how to avoid this? I am mentioning commons-logging-1.1 as my dependency in the pom.xml, and have suppressed the other versions of commons logging which were getting packaged as transitive dependencies of project dependencies using tag in dependency taf. Same is happening with commons-digester and other dependencies. Regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven with Eclipse
I was not able to locale 0.12 version of m2eclipse plug at http://m2eclipse.codehaus.org/update-dev/plugins/ Ben I would definitely try the plug in you had mentioned because my experience with m2eclipse plug in for eclipse is not so "cool" in terms of reliability while working from Eclipse console ( in case of downloading artifacts, searching the repository and compiling results etc. ). The problem is resolved for 0.11 version as well, there was some problem with Linking of sources in eclipse, which is tackled now. Thanks a ton. Regards, Amit On Jan 29, 2008 3:43 PM, Thomas Lutz <[EMAIL PROTECTED]> wrote: > You could try > > http://code.google.com/p/q4e/ > > Other maven plugin, not as well known as mevenide or M2Eclipse plugin, > but for me it works a lot better... > > Tom > > Ben Lidgey schrieb: > > > There is a newer version of the M2Eclipse plugin (0.0.12) which might make > > a difference. Also, there are settings in Eclipse to control the > > highlighting (see Windows-Preferences-Java-Editor and see if the "Report > > problems as you type" box is checked). > > > > Ben > > > > > >> -Original Message- > >> From: amit kumar [mailto:[EMAIL PROTECTED] > >> Sent: 29 January 2008 08:07 > >> To: Maven Users List > >> Subject: Maven with Eclipse > >> > >> Hi, > >> I am using maven plug-in with myeclipse 6.0. But while coding > >> even if I add rubbish to the code, I can not see any error > >> line(the usual red line at the point of syntactic error). > >> Could anyone help with that? > >> > >> I am using the org.maven.ide.eclipse_0.0.11.20070603-1200 plug in. > >> Regards, > >> Amit > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > This e-mail is confidential and intended solely for the use of the > > individual(s) to whom it is addressed. Any views or opinions expressed are > > those of the author. If you are not the intended recipient, please be > > advised that any use, dissemination, printing or copying of this email is > > strictly prohibited. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven with Eclipse
Hi, I am using maven plug-in with myeclipse 6.0. But while coding even if I add rubbish to the code, I can not see any error line(the usual red line at the point of syntactic error). Could anyone help with that? I am using the org.maven.ide.eclipse_0.0.11.20070603-1200 plug in. Regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any tool available for generating docs from pom.xml?
Thanks Nick. I am sorry for my lack of expression. But what mvn site generates is what I am expected to report about by in a doc rather than a web page ( I told you it would sound stupid). Thanks a ton for the kind help. regards, Amit On Jan 23, 2008 8:09 PM, <[EMAIL PROTECTED]> wrote: > Ok, to make it clear, what do you want to report about. > > The dependencies report show all your dependencies, the jdepend report indeed > reports about packages, and so there are numerous more reports. > > If you can make clear what you want, maybe that will help finding a solution. > > With regards, > > Nick Stolwijk > > > -Original Message- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Wed 1/23/2008 3:37 PM > To: Maven Users List > > Subject: Re: Any tool available for generating docs from pom.xml? > > Isn't jdepend plug in more about the packages and classes of the > build? Not sure. Just what I got after seeing the report it generated. > > On Jan 23, 2008 6:27 PM, Guillaume Lederrey > <[EMAIL PROTECTED]> wrote: > > You have the jdepend plugin that will do some analysis of your > > dependencies (http://mojo.codehaus.org/jdepend-maven-plugin/). And I > > think that the maven-dependency-plugin provide a report as well ... > > > > > > On 23/01/2008, amit kumar <[EMAIL PROTECTED]> wrote: > > > No reports for my dependencies, like the expectation is something like > > > having a table generated with artifact name and the versions... ( if > > > there is something more than that in reports its fine, but that is the > > > minimum). > > > > > > Regards, > > > Amit > > > > > > On Jan 23, 2008 2:02 PM, Stephen Connolly > > > <[EMAIL PROTECTED]> wrote: > > > > The site plugin's info reports? > > > > > > > > > > > > On Jan 23, 2008 7:58 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi, > > > > > I know this would sound stupid ( as it sounded to me when asked ), but > > > > > is there any such tool using which you can generate a doc in tabular > > > > > format with the information stored in pom.xml mainly the dependency > > > > > part. > > > > > > > > > > Please let me know in case there exists one tool. > > > > > > > > > > Regards, > > > > > Amit > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Jabber : [EMAIL PROTECTED] > > Skype : Guillaume.Lederrey > > Projects : > > * http://rwanda.wordpress.com/ > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any tool available for generating docs from pom.xml?
Isn't jdepend plug in more about the packages and classes of the build? Not sure. Just what I got after seeing the report it generated. On Jan 23, 2008 6:27 PM, Guillaume Lederrey <[EMAIL PROTECTED]> wrote: > You have the jdepend plugin that will do some analysis of your > dependencies (http://mojo.codehaus.org/jdepend-maven-plugin/). And I > think that the maven-dependency-plugin provide a report as well ... > > > On 23/01/2008, amit kumar <[EMAIL PROTECTED]> wrote: > > No reports for my dependencies, like the expectation is something like > > having a table generated with artifact name and the versions... ( if > > there is something more than that in reports its fine, but that is the > > minimum). > > > > Regards, > > Amit > > > > On Jan 23, 2008 2:02 PM, Stephen Connolly > > <[EMAIL PROTECTED]> wrote: > > > The site plugin's info reports? > > > > > > > > > On Jan 23, 2008 7:58 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > I know this would sound stupid ( as it sounded to me when asked ), but > > > > is there any such tool using which you can generate a doc in tabular > > > > format with the information stored in pom.xml mainly the dependency > > > > part. > > > > > > > > Please let me know in case there exists one tool. > > > > > > > > Regards, > > > > Amit > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jabber : [EMAIL PROTECTED] > Skype : Guillaume.Lederrey > Projects : > * http://rwanda.wordpress.com/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any tool available for generating docs from pom.xml?
No reports for my dependencies, like the expectation is something like having a table generated with artifact name and the versions... ( if there is something more than that in reports its fine, but that is the minimum). Regards, Amit On Jan 23, 2008 2:02 PM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > The site plugin's info reports? > > > On Jan 23, 2008 7:58 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > Hi, > > I know this would sound stupid ( as it sounded to me when asked ), but > > is there any such tool using which you can generate a doc in tabular > > format with the information stored in pom.xml mainly the dependency > > part. > > > > Please let me know in case there exists one tool. > > > > Regards, > > Amit > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Any tool available for generating docs from pom.xml?
Hi, I know this would sound stupid ( as it sounded to me when asked ), but is there any such tool using which you can generate a doc in tabular format with the information stored in pom.xml mainly the dependency part. Please let me know in case there exists one tool. Regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sending email notification to Owners
Hi Michael, While adding the project in continuum I have to add choosing the option of "load the parent project recursively in case of multi module project", otherwise it doesn't get build. But after I select this option, the added project doesn't show me sub modules to add notifiers to. Only the parent module is visible and the notification parameter can be set only on the parent project. So i was not able to add the notifiers from continuum. Regards, Amit On Jan 19, 2008 12:19 AM, Michael Meyer <[EMAIL PROTECTED]> wrote: > Hi Amit, > you say you are using continuum 1.1. Can you not just add a different > notifier to each module? > > > But I was told by a colleague of mine that there is something > > in maven as well which would let you add the information about > > the owner and the email address in the pom.xml > Your colleague probably ment the "Continuus Integration" section of the > pom: http://maven.apache.org/pom.html#Continuous_Integration_Management > > michael > > amit kumar schrieb: > > Ditto mick, ditto! That's what I am looking for but no clue yet. > > > > Regards, > > Amit > > > > On Jan 18, 2008 8:59 PM, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > >> I have the same question. sort-of: > >> > >> I have: > >> > >> pom.xml > >>|--->module 1 pom.xml > >> |--->[EMAIL PROTECTED] > >>|--->module 2 pom.xml > >> |--->[EMAIL PROTECTED] > >> > >> > >> Is it possible to have developer2 emailed if module1 fails and developer1 > >> emailed when project1 fails? > >> > >> > >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to handle Incremental Versions
I am using buildnumber plugin now to append timestamp to the builds. But at continuous integration ( Continuum) I am facing the problem because in the pom.xml for any dependency I have specified a particular version say 1.0, but after using the buildnumber plugin the builds have a different version everytime(varying with time). How to handle this? On Jan 21, 2008 12:34 PM, amit kumar <[EMAIL PROTECTED]> wrote: > Hi, > If I use buildnumber plugin to have builds with versions in > incremental fashion, is there any way to handle this changed version > of the artifact in the pom.xmls of other artifacts which are dependent > on such a particular module(with incremental versions) > > Regards, > Amit > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to handle Incremental Versions
Hi, If I use buildnumber plugin to have builds with versions in incremental fashion, is there any way to handle this changed version of the artifact in the pom.xmls of other artifacts which are dependent on such a particular module(with incremental versions) Regards, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Avoid Dependency version
Hi, The reason for I thinking about not having version component in the tag might result in a better version control in terms of same version being used across the different modules of the project. Though not very sure if I am genuine enough when I think that. Actually when I want to avoid dependency versions, I want to do it in context of an individual project(irrespective of chil-parent relationship).My question was that for instance if I am using commons-logging in my dependency ... commons-logging commons-logging 1.0.4 Is there a way around to avoid the version component so that the latest version gets fetched from the repository? And as Wayne pointed out , is it a good thing to think about? Regards, Amit On Jan 19, 2008 10:44 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > I almost replied with this same content but decided against it. > > Amit, you realize that you are heading down a very ugly path if you > use any of these options, and you will get builds that are all but > impossible to reproduce etc, right? > > Wayne > > > > > On 1/19/08, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > You can use dependencyManagment in a parent pom to avoid specifying the > > version in all your child poms. If you really want the "latest" you have > > two choices: > > LATEST - latest snapshot > > RELEASE - latest release > > > > Or you could specify a range like [0,) > > > > -Original Message- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 18, 2008 8:38 AM > > To: Maven Users List > > Subject: Avoid Dependency version > > > > Hi, > > Can I make it possible for my dependencies(jar files) declared in > > tags, not have version. Just like in case of plugin it > > happens, > > the latest on gets fetched? > > When I don't put a version in my dependency tag, it throws error. > > > > Regards, > > Amit > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Sending email notification to Owners
Ditto mick, ditto! That's what I am looking for but no clue yet. Regards, Amit On Jan 18, 2008 8:59 PM, Mick Knutson <[EMAIL PROTECTED]> wrote: > I have the same question. sort-of: > > I have: > > pom.xml >|--->module 1 pom.xml > |--->[EMAIL PROTECTED] >|--->module 2 pom.xml > |--->[EMAIL PROTECTED] > > > Is it possible to have developer2 emailed if module1 fails and developer1 > emailed when project1 fails? > > > > On Jan 17, 2008 9:27 PM, amit kumar <[EMAIL PROTECTED]> wrote: > > > :-). We are as well using continuum 1.1. But isn't there a possibility > > that > > something else has failed rather than last commit? Because we are doing > > daily build ( once). > > That's why was looking for something with in maven where i could specify > > all > > this information in pom.xml only. > > > > > > On Jan 17, 2008 11:52 PM, Jeff Mutonho <[EMAIL PROTECTED]> wrote: > > > > > On Jan 17, 2008 5:16 PM, Martin Alejandro Villalobos < > > > [EMAIL PROTECTED]> wrote: > > > > > > > Jeff, Continuum 1.1 have a new option in the notifiers section named > > > > "Send a mail to latest committers" > > > > I hope that it be helpful. > > > > > > > > Regards. > > > > \Martin. > > > > > > > > > > > Thanks Martin , but I think the "target member of the audience" here > is > > > Amit :) > > > > > > > > > -- > > > > > > "Don't take the name of root in vain." > > > > > > Jeff Mutonho > > > Cape Town > > > South Africa > > > > > > GoogleTalk : ejbengine > > > Skype: ejbengine > > > Registered Linux user number 366042 > > > > > > > > > -- > Thanks, > Mick Knutson > > http://www.baselogic.com > http://www.blincmagazine.com > http://www.djmick.com > http://www.myspace.com/mickknutson > http://www.myspace.com/BLiNCMagazine > http://tahoe.baselogic.com > --- >
Re: how can I to use build time in pom files
You can use buildnumber-maven-plugin, for this but i was able to have
date+time... tried only time format but it wasn't running. If this solves
your purpose lemme know, I will share the relevant portion of my pom.
On Jan 18, 2008 7:58 PM, Rex Huang <[EMAIL PROTECTED]> wrote:
> Does maven has build time property, which I can use in pom files
> ${build time}
>
> BR//Rex
>
Avoid Dependency version
Hi, Can I make it possible for my dependencies(jar files) declared in tags, not have version. Just like in case of plugin it happens, the latest on gets fetched? When I don't put a version in my dependency tag, it throws error. Regards, Amit
Re: M2 Cargo Plugin
n 18, 2008 3:17 PM, Daniele De Francesco <[EMAIL PROTECTED]> wrote: > Hi, > > the id of the container is "jboss42x"...assure you have the latest version > of maven 2 cargo plugin...alternatively do a full build yourself with the > svn code...take a look at > > http://cargo.codehaus.org/Importing+sources > > hope this helps. > > Cheers > Daniele > > > > On Jan 18, 2008 10:09 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > Hi, > > What is the containerId for JBoss 4.2.0GA? Is it same jboss4x or > > different? > > Because I tried fetching the plugin without version name and maven did > > download something newer than 0.3-SNAPSHOT but it threw the same error > > when > > I used container id jboss4x. > > > > Regards, > > Amit > > > > On Jan 18, 2008 11:00 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > > > Thanks a ton. But using an older version of JBoss would not be a > > > possibility reason being the product already on this version. > > > > > > > > > > > > On Jan 17, 2008 9:35 PM, David J. M. Karlsen < [EMAIL PROTECTED]> > > > wrote: > > > > > > > On Thu, 17 Jan 2008, amit kumar wrote: > > > > > > > > > Hi, > > > > > Anyone aware of any online documentation for M2 Cargo plugin for > > > > JBoss. I > > > > > tried looking for it ,but in vain. > > > > > If someone has already worked on it, please guide. > > > > > > > > > > I am using maven 2.0.7 > > > > > Windows XP > > > > > JBoss 4.2.0GA > > > > > > > > Try the cargo users/dev list - there's a new commiter working on > this. > > > > > > > > > > > > David J. M. Karlsen - +47 90 68 22 43 > > > > http://www.davidkarlsen.com > > > > http://mp3.davidkarlsen.com > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > >
Re: M2 Cargo Plugin
Hi, What is the containerId for JBoss 4.2.0GA? Is it same jboss4x or different? Because I tried fetching the plugin without version name and maven did download something newer than 0.3-SNAPSHOT but it threw the same error when I used container id jboss4x. Regards, Amit On Jan 18, 2008 11:00 AM, amit kumar <[EMAIL PROTECTED]> wrote: > Thanks a ton. But using an older version of JBoss would not be a > possibility reason being the product already on this version. > > > > On Jan 17, 2008 9:35 PM, David J. M. Karlsen < [EMAIL PROTECTED]> > wrote: > > > On Thu, 17 Jan 2008, amit kumar wrote: > > > > > Hi, > > > Anyone aware of any online documentation for M2 Cargo plugin for > > JBoss. I > > > tried looking for it ,but in vain. > > > If someone has already worked on it, please guide. > > > > > > I am using maven 2.0.7 > > > Windows XP > > > JBoss 4.2.0GA > > > > Try the cargo users/dev list - there's a new commiter working on this. > > > > > > David J. M. Karlsen - +47 90 68 22 43 > > http://www.davidkarlsen.com > > http://mp3.davidkarlsen.com > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: M2 Cargo Plugin
Thanks a ton. But using an older version of JBoss would not be a possibility reason being the product already on this version. On Jan 17, 2008 9:35 PM, David J. M. Karlsen <[EMAIL PROTECTED]> wrote: > On Thu, 17 Jan 2008, amit kumar wrote: > > > Hi, > > Anyone aware of any online documentation for M2 Cargo plugin for JBoss. > I > > tried looking for it ,but in vain. > > If someone has already worked on it, please guide. > > > > I am using maven 2.0.7 > > Windows XP > > JBoss 4.2.0GA > > Try the cargo users/dev list - there's a new commiter working on this. > > > David J. M. Karlsen - +47 90 68 22 43 > http://www.davidkarlsen.com > http://mp3.davidkarlsen.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Re: Sending email notification to Owners
:-). We are as well using continuum 1.1. But isn't there a possibility that something else has failed rather than last commit? Because we are doing daily build ( once). That's why was looking for something with in maven where i could specify all this information in pom.xml only. On Jan 17, 2008 11:52 PM, Jeff Mutonho <[EMAIL PROTECTED]> wrote: > On Jan 17, 2008 5:16 PM, Martin Alejandro Villalobos < > [EMAIL PROTECTED]> wrote: > > > Jeff, Continuum 1.1 have a new option in the notifiers section named > > "Send a mail to latest committers" > > I hope that it be helpful. > > > > Regards. > > \Martin. > > > > > Thanks Martin , but I think the "target member of the audience" here is > Amit :) > > > -- > > "Don't take the name of root in vain." > > Jeff Mutonho > Cape Town > South Africa > > GoogleTalk : ejbengine > Skype: ejbengine > Registered Linux user number 366042 >
Re: M2 Cargo Plugin
Hi, I finally got to see the documentation on how to use cargo ( did not find an example for jboss), but when I put the required container configuration ( the most basic one, just as first to test the start of the server). I am seeing the below error at console [INFO] [talledLocalContainer] 18:05:51,359 INFO [Server] Server Home Dir: E:\jobsstest\target\jboss4x [INFO] [talledLocalContainer] 18:05:51,359 INFO [Server] Server Home URL: file:/E:/jobsstest/target/jboss4x/ [INFO] [talledLocalContainer] 18:05:51,359 INFO [Server] Server Log Dir: E:\jobsstest\target\jboss4x\log [INFO] [talledLocalContainer] 18:05:51,359 INFO [Server] Server Temp Dir: E:\jobsstest\target\jboss4x\tmp [INFO] [talledLocalContainer] 18:05:51,359 INFO [Server] Root Deployment Filename: jboss-service.xml [INFO] [talledLocalContainer] 18:05:53,468 INFO [ServerInfo] Java version: 1.5.0_08,Sun Microsystems Inc. [INFO] [talledLocalContainer] 18:05:53,468 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_08-b03,Sun Microsystems Inc. [INFO] [talledLocalContainer] 18:05:53,468 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 [INFO] [talledLocalContainer] 18:05:55,734 INFO [Server] Core system initialized [INFO] [talledLocalContainer] 18:06:02,531 INFO [ServiceBindingManager] Initializing store [INFO] [talledLocalContainer] 18:06:02,531 INFO [ServiceBindingManager] Using StoreURL: file:/E:/jobsstest/target/jboss4x/conf/cargo- [INFO] [talledLocalContainer] 18:06:04,734 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml [INFO] [talledLocalContainer] 18:06:05,328 WARN [ServiceController] Problem starting service jboss:service=Naming [INFO] [talledLocalContainer] java.lang.NullPointerException [INFO] [talledLocalContainer] at org.jnp.server.Main.getNamingInstance( Main.java:301) [INFO] [talledLocalContainer] at org.jnp.server.Main.initJnpInvoker( Main.java:354) [INFO] [talledLocalContainer] at org.jnp.server.Main.start(Main.java:316) [INFO] [talledLocalContainer] at org.jboss.naming.NamingService.startService(NamingService.java:284) [INFO] [talledLocalContainer] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart( ServiceMBeanSupport.java:289) [INFO] [talledLocalContainer] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle( ServiceMBeanSupport.java:245). I am using the below basic configuration my pom.xml jobsstest package org.codehaus.cargo cargo-maven2-plugin 0.3-SNAPSHOT jboss4x E:/jboss-4.2.0.GA Any help? Amit On Jan 17, 2008 5:32 PM, amit kumar <[EMAIL PROTECTED]> wrote: > Hi, > Anyone aware of any online documentation for M2 Cargo plugin for JBoss. I > tried looking for it ,but in vain. > If someone has already worked on it, please guide. > > I am using maven 2.0.7 > Windows XP > JBoss 4.2.0GA > > regards, > Hemant Malik >
M2 Cargo Plugin
Hi, Anyone aware of any online documentation for M2 Cargo plugin for JBoss. I tried looking for it ,but in vain. If someone has already worked on it, please guide. I am using maven 2.0.7 Windows XP JBoss 4.2.0GA regards, Hemant Malik
Re: Sending email notification to Owners
Oh okay, yes that sounds pretty genuine. I am using continuum with maven. But I was told by a colleague of mine that there is something in maven as well which would let you add the information about the owner and the email address in the pom.xml, and that information would be used to send a notification to particular owner of that module. Regards, Amit On Jan 17, 2008 1:58 PM, Jeff Mutonho <[EMAIL PROTECTED]> wrote: > On Jan 17, 2008 8:57 AM, amit kumar <[EMAIL PROTECTED]> wrote: > > > Hi, > > I am using Maven 2, I want to send email notifications to the respective > > owners of the sub modules, if possible with error trace. How do I do > that? > > > > Could someone help on that? > > > > Regards, > > Amit > > > I'm not sure if this is possible with Maven on its own , but I'm using > Maven with Hudson , and Hudson sends an e-mail to the last person to > commit > , whenever there's a broken build(i think the assumption is the last > person > to commit would've broken the build) > > > > -- > > "Don't take the name of root in vain." > > Jeff Mutonho > Cape Town > South Africa > > GoogleTalk : ejbengine > Skype: ejbengine > Registered Linux user number 366042 >
