Re: Recompile dependencies
Anybody ?? Recompile projects children? -- View this message in context: http://maven.40175.n5.nabble.com/Recompile-dependencies-tp5682998p5683274.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Recompile dependencies
Hi .. I have a question. I am new to maven. : ( I have a project J2ee integration with maven, and I have projects as dependencies. When I change my projects children, the main project there are no major design changes, or do I have to manually recompile the projects children. How to compile the main project and make new jar of the project dependencies? Thanks a lot. Sorry, my english is poor :) -- View this message in context: http://maven.40175.n5.nabble.com/Recompile-dependencies-tp5682998.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release process does resolve SNAPSHOT dependencies
Humm, ok! Is there anything that I can do to change this? Advices in how organize the projects? How about add a flag to the release-plugin indicating to reactor that it can resolve the plugin dependencies if such dependency is generate during the build? On Sat, Feb 12, 2011 at 3:26 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > that is a circular reference... the big is that you are allowed to make > such > a cycle. > > the reason why this is not allowed is that maven constructs the build plan > up front, and when a plugin depends on a module from the reactor, then the > build plan could (in theory) be affected based on the result of building... > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 12 Feb 2011 17:02, "Thiago Moreira (timba)" > wrote: > > Hi there, > > > > I have a multi module project (https://github.com/floggy/parent) that > has > > two submodules. In the parent project I make reference to one submodule > like > > this: > > > > > > > > org.apache.maven.plugins > > maven-checkstyle-plugin > > true > > > > * * > > * org.floggy* > > * build-tools* > > * 0.0.2-SNAPSHOT* > > * * > > > > > > checkstyle-checks-configuration.xml > > > > > > > > > > When I release the whole project the release plugin does not resolve the > > SNAPSHOT version of my dependency when it is declared as a dependency of > a > > plugin. Is there a way to force Maven to do that? Seems that there is the > > same problem with the dependecyManagement section: > > http://jira.codehaus.org/browse/MRELEASE-649 > > Ideas? Is this a bug? > > > > Thanks in advance >
Release process does resolve SNAPSHOT dependencies
Hi there, I have a multi module project (https://github.com/floggy/parent) that has two submodules. In the parent project I make reference to one submodule like this: org.apache.maven.plugins maven-checkstyle-plugin true * * * org.floggy* * build-tools* * 0.0.2-SNAPSHOT* * * checkstyle-checks-configuration.xml When I release the whole project the release plugin does not resolve the SNAPSHOT version of my dependency when it is declared as a dependency of a plugin. Is there a way to force Maven to do that? Seems that there is the same problem with the dependecyManagement section: http://jira.codehaus.org/browse/MRELEASE-649 Ideas? Is this a bug? Thanks in advance
Re: Defining a project name when creating it from an archetype.
Hey Ryan,
Yes, I'm working on Liferay Hook and Ext plugins port to Maven.
I realized that I can do something like you described. Thanks for the input.
Thiago Moreira
On Tue, Dec 7, 2010 at 5:52 PM, Ryan Connolly wrote:
> Hi Thiago:
> For starters let me take a guess and say that the liferay archetypes
> will soon have a new addition? Secondly, I am no archetype expert but I'm
> guessing by the docs at
> guide-creating-archetypes<
> http://maven.apache.org/guides/mini/guide-creating-archetypes.html>
> you
> could simply add the desired extension following the artifactId property in
> the prototype POM. For example:
> ${artifactId}-hook
>
> This would have the drawback of users who actually follow the required
> naming convention of hooks ending up with an artifactId of
> my-artifact-hook-hook. Of course users who encounter the aforementioned
> drawback would likely regenerate without the convention and end up with a
> nicely named artifact.
>
> I have not tried this but it may be an option for you.
>
> -Ryan
>
>
>
> On Tue, Dec 7, 2010 at 6:35 PM, Thiago Moreira (timba) <
> tmoreira2...@gmail.com> wrote:
>
> > Hi there!
> >
> > I'm building an archetype and one thing that I need to take in account
> > when creating an instance of the archetype is the directory's name
> > generated. This is important because the artifact generated will be used
> in
> > another system that the name is important. Is there way to force the
> > articfactId to be a format like my-articfact*-hook*? The bold part is
> that
> > is important for me.
> >
> > Thanks in advance
> >
> > Thiago Moreira
> >
>
>
>
> --
> �...@n
>
Defining a project name when creating it from an archetype.
Hi there! I'm building an archetype and one thing that I need to take in account when creating an instance of the archetype is the directory's name generated. This is important because the artifact generated will be used in another system that the name is important. Is there way to force the articfactId to be a format like my-articfact*-hook*? The bold part is that is important for me. Thanks in advance Thiago Moreira
Re: Maven 3 and site generation
I think I'm in the same boat... I found the following resources that helped me out to fix some of the problems https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html <https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html> http://maven.apache.org/doxia/references/doxia-apt.html <http://maven.apache.org/doxia/references/doxia-apt.html> Hope that help My best Thiago Moreira On Sat, Oct 16, 2010 at 4:05 AM, Olivier Lamy wrote: > Hi, > Yes I agree, it's very noisy : the report > project-info-reports:dependencies must ignore target/classes > directories coming from reactors. > Can you load a jira entry ? > > Thanks, > -- > Olivier > http://twitter.com/olamy > http://www.linkedin.com/in/olamy > > > 2010/10/16 Jörg Hohwiller : > > Hi there, > > > > I went to the official maven 3.0 release and build works fine. > > Log-messages and performance have improved. > > > > However site generation is exorbitant slow and produces wired exceptions > > such as > > FileNotFoundException: .../target/classes (permission denied) > > ... > >at java.util.zip.ZipFile.(ZipFile.java:114) > > ... > >at > > > org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:283) > > > > I use > > maven-site-plugin:3.0-beta2 > > maven-project-info-reports-plugin:2.2 > > maven-javadoc-plugin:2.7 > > > > Do you have success-stories with multi-project site generation and m3? > > Or am I on an early adopters terrain here and should better stay > > with m2, even though official 3.0 has been released? > > > > Best regards > > Jörg > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How to take archetypeVersion in archetype-resources ?
Hi Khin,
How did you manage this problem? I'm trying to do the same thing.
Thanks
Thiago Moreira
On Fri, Jun 11, 2010 at 11:29 AM, NGUYEN Cong Kinh <
cong_kinh.ngu...@it-sudparis.eu> wrote:
> Hi everybody,
>
> I create a maven-archetype as the following:
>
> - myArchetype
> + pom.xml (1)
> + src/main/resources
> + META-INF...
> + archetype-resources
> - pom.xml (2)
> - src/...
>
>
>
> In the second POM (pom.xml - 2) which module will be generated by my
> maven-archetype, I want to set the version of one dependency to the same
> version with my maven - archetype. Could you any ideas for that? (I tried to
> use ${archetypeVersion}, but it seems to me that this isn't correct).
>
> For example, I define the second POM as following:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> 4.0.0
> ${groupId}
> ${artifactId}
> jar
> ${version}
> Your custom project
>
>
>
> my groupID
> my artifactID
> what will be placed here ?
>
>
> ...
>
>
>
>
> Thanks in advance,
> Kinh
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Dependency plugin strange behavior
Hi Stephen,
Thank you for the explanation. The documentation is not clear about which
dependency the plugin will work on (from the repository or produced by the
build). For those of you interested in the configuration that fixed my issue
here it go:
copy-dependencies
process-sources
copy-dependencies
floggy-persistence-weaver
${basedir}/target/site/demo
false
true
true
true
unpack
process-sources
unpack-dependencies
floggy-persistence-weaver
${basedir}/target/site
schema/*
Thanks!
Thiago Moreira
On Tue, Jan 26, 2010 at 3:18 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> dependency:unpack works on artifacts that are not produced as part of your
> build and are not listed as dependencies, as a result you must specify the
> full GAV coordinates to resolve the artifact, and if you are foolish enough
> to use it for an artifact that is produced as part of the same build that
> your project is part of, then you will not be able to release that
> multi-module project with the maven-release-plugin.
>
> dependency:unpack-dependencies works on artifacts that are produced in the
> reactor (i.e. all the projects in the multi-module build that your project
> is part of).
>
> This same pairing exists with dependency:copy vs
> dependency:copy-dependencies
>
> -Stephen
>
> 2010/1/26 Thiago Moreira (timba)
>
> > Hi there,
> >
> > I'm facing a strange behavior with the dependency plugin. Here is my
> > configuration
> >
> >
> > org.apache.maven.plugins
> > maven-dependency-plugin
> > 2.1
> >
> >
> > copy-dependencies
> > process-sources
> >
> > copy-dependencies
> >
> >
> > ${basedir}/target/site/demo
> > false
> > true
> > true
> > true
> >
> >
> >
> > unpack
> > process-sources
> >
> > unpack
> >
> >
> >
> >
> > net.sourceforge.floggy
> > floggy-persistence-weaver
> > ${basedir}/target/site
> > schema/*
> >
> >
> >
> >
> >
> >
> >
> > For the copy-dependencies execution it works fine but for the unpack
> > execution it claims that cannot revolve the dependency
> > net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
> > declared at dependencies section and it is a sibling project of the
> current
> > one in a multi module project. The only difference that I can observe is
> > that in one execution (unpack ID) I made an explicit reference to the
> > dependency.
> > Any clue why? Any workaround?
> >
> > Thanks
> >
> > Thiago Moreira
> >
>
Dependency plugin strange behavior
Hi there,
I'm facing a strange behavior with the dependency plugin. Here is my
configuration
org.apache.maven.plugins
maven-dependency-plugin
2.1
copy-dependencies
process-sources
copy-dependencies
${basedir}/target/site/demo
false
true
true
true
unpack
process-sources
unpack
net.sourceforge.floggy
floggy-persistence-weaver
${basedir}/target/site
schema/*
For the copy-dependencies execution it works fine but for the unpack
execution it claims that cannot revolve the dependency
net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
declared at dependencies section and it is a sibling project of the current
one in a multi module project. The only difference that I can observe is
that in one execution (unpack ID) I made an explicit reference to the
dependency.
Any clue why? Any workaround?
Thanks
Thiago Moreira
Maven 3.0 ProjectCycleException
Hi there,
I have a project that contains a build-tools subproject used only to store
configuration files for checkstyle, jalopy and so forth... the parent
project contains plugins that reference the build-tools subproject and the
subproject reference the parent in its parent tag. I'm moving to the new
version of Maven (alpha5) and I got this exception
[INFO] Scanning for projects...
[ERROR] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='net.sourceforge.floggy:build-tools:1.3.0-SNAPSHOT'}' and
'Vertex{label='net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT'}' introduces to
cycle in the graph net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT -->
net.sourceforge.floggy:build-tools:1.3.0-SNAPSHOT -->
net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectCycleException
How can I fix my issue? What is the common sense to solve this cyclic
reference??
BTW this page doesn't exist
http://cwiki.apache.org/confluence/display/MAVEN/ProjectCycleException
Cheers
Thiago Moreira
Re: Maven 2.0.8 + maven-compiler-plugin 2.0.2 issue
Hey all, This is not an issue any more. I was able to update the environment to a 2.2.x version of Maven. Thanks anyway! Thiago Moreira On Sun, Nov 15, 2009 at 4:02 PM, Wayne Fay wrote: > > Thanks for confirmed that. Could you explain a little bit more how to > > workaround, I didn't get it. > > You currently have: > plugins > +-plugin > +-+-executions > +-+-+-execution > +-+-+-+-configuration > > You should change that to (below) if you want to apply the > configuration to the default execution: > plugins > +-plugin > +-+-configuration > > Then if you have additional executions, you can specify them with > their own configurations. If the configurations are not compatible, > make sure you overwrite the incompatible parts in the execution > config. Clearer now? > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 2.0.8 + maven-compiler-plugin 2.0.2 issue
Hi Stephen,
Thanks for confirmed that. Could you explain a little bit more how to
workaround, I didn't get it.
Thanks
Thiago Moreira
On Sun, Nov 15, 2009 at 8:35 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> 2.0.8 does not support default-cli execution
>
> the workaround is to specify the defaults outside an execution and if
> necessary revert them back within any lifecycle bound executions
>
> Sent from my [rhymes with tryPod] ;-)
>
>
> On 14 Nov 2009, at 23:24, "Thiago Moreira (timba)"
> wrote:
>
> Hi there,
>>
>> I have the following configuration for the maven-compiler-plugin
>>
>>
>> maven-compiler-
>> plugin
>>
>>
>> default-compile
>> compile
>>
>> 1.3
>> 1.1
>> -g:none
>>
>>
>>
>>
>> ${settings.localRepository}/org/microemu/cldcapi11/${me2Version}/cldcapi11-${me2Version}.jar${path.separator}${settings.localRepository}/org/microemu/midpapi20/${me2Version}/midpapi20-${me2Version}.jar
>>
>>
>>
>>
>> compile
>>
>>
>>
>> default-testCompile
>> testCompile
>>
>> 1.3
>> 1.3
>>
>>
>> testCompile
>>
>>
>>
>>
>>
>> The thing is the configuration does NOT apply to the default executions
>> in
>> Maven 2.0.8, it works fine in 2.2.1. Is it expected? The feature of
>> overriding the default executions was added between these version? Is
>> there
>> a workaround?
>>
>> Thanks
>>
>> Thiago Moreira
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Maven 2.0.8 + maven-compiler-plugin 2.0.2 issue
Hi there,
I have the following configuration for the maven-compiler-plugin
maven-compiler-
plugin
default-compile
compile
1.3
1.1
-g:none
${settings.localRepository}/org/microemu/cldcapi11/${me2Version}/cldcapi11-${me2Version}.jar${path.separator}${settings.localRepository}/org/microemu/midpapi20/${me2Version}/midpapi20-${me2Version}.jar
compile
default-testCompile
testCompile
1.3
1.3
testCompile
The thing is the configuration does NOT apply to the default executions in
Maven 2.0.8, it works fine in 2.2.1. Is it expected? The feature of
overriding the default executions was added between these version? Is there
a workaround?
Thanks
Thiago Moreira
Execution sequence of three plugins on the same phase: process-classes
Hi there, I have three plugins that must be executed on the same phase (process-classes). How can I set the sequence on each one will be executed? Thanks in advance! Thiago Moreira
Re: Oddness with release:prepare
I used the workaround "svn up -r HEAD" to fix it... and than mvn release:prepare -Dresume=true to finish the preparation... Got the answer with some one on here... Cheers On Fri, Jan 30, 2009 at 3:22 PM, James CE Johnson wrote: > You nailed it. That box has the 1.5.3 svn client. So I can leave my > workaround in place until SVN gets fixed or roll back to 1.4. The server > is still 1.4.x so rolling back the client wouldn't be any big thing. > > Thanks for the quick info! > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > What version of SVN are you using? I'm betting it's 1.5.1+. There's a > > bug where the > > release plugin can't run with SVN 1.5.1+. 1.4.x works fine, as does > 1.5.0 > > (but I hear > > that has some other bad bugs). > > > > This is a real bummer, since I would love to update to SVN 1.5, but I'm > > stuck on 1.4. > > > > I've been following the bug here: > > > > http://jira.codehaus.org/browse/SCM-406 > > > > Apparently it's an SVN thing, not an scm plugin one, but the scm bug has > a > > thorough > > discussion and links to more relevant places. > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Problems with release:prepare on the resolution of a dependency with "test" classifier
Thank you Barrie! Now it is working fine BUT I'm getting a new error... [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label floggy-1.2.0... [INFO] Executing: svn --non-interactive copy --file /tmp/maven-scm-200887962.commit . https://floggy.svn.sourceforge.net/svnroot/floggy/tags/floggy-1.2.0 [INFO] Working directory: /home/tmoreira2020/projects/floggy/trunk-fr2536956 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svnroot/floggy/tags/floggy-1.2.0/eclipse-floggy-feature/pom.xml' already exists [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 22 seconds [INFO] Finished at: Wed Jan 28 00:24:11 PST 2009 [INFO] Final Memory: 9M/82M [INFO] That file don't exist! You can check the project structure here http://floggy.svn.sourceforge.net/viewvc/floggy/ Has anyone else experienced something like this?? Cheers On Tue, Jan 27, 2009 at 6:36 PM, Barrie Treloar wrote: > On Wed, Jan 28, 2009 at 4:34 AM, Thiago Moreira (timba) > wrote: > > Ok, I took a look on the source code of the maven-release-plugin and > there > > is no way to set the preparationGoals from the command line!!! > > > > The method mergeCommandLineConfig< > http://maven.apache.org/plugins/maven-release-plugin/xref/org/apache/maven/plugins/release/PrepareReleaseMojo.html#181 > >of > > the PrepareReleaseMojo class only merge the releaseVersions and > > developmentVersions properties. > > We have the same scenario that you have and we are using release fine. > > You may want to use > >MYGROUP >MYARTIFACT >MYVERSION >test-jar >test > > > type = test-jar > instead of classifier = test. > > There are some wierd inconsistencies with this. > > Straight from our release page in our wiki: > mvn release:prepare > -Dmaven.scm.provider.cvs.implementation=cvs_native > -DpreparationGoals=clean,install -Dusername= > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Problems with release:prepare on the resolution of a dependency with "test" classifier
Ok, I took a look on the source code of the maven-release-plugin and there is no way to set the preparationGoals from the command line!!! The method mergeCommandLineConfig<http://maven.apache.org/plugins/maven-release-plugin/xref/org/apache/maven/plugins/release/PrepareReleaseMojo.html#181>of the PrepareReleaseMojo class only merge the releaseVersions and developmentVersions properties. On Tue, Jan 27, 2009 at 9:31 AM, Thiago Moreira (timba) < tmoreira2...@gmail.com> wrote: > > The workaround is not working for me! I tried mvn release:prepare > -DpreparationGoals="clean install" without success. Any other thoughts?? > > > On Sun, Jan 25, 2009 at 11:44 PM, Barrie Treloar wrote: > >> On Mon, Jan 26, 2009 at 5:03 PM, Thiago Moreira (timba) >> wrote: >> > Hi there, >> > >> > I have a multi module project and one of the sub modules produce two >> > artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is >> built >> > using this configuration: >> > >> > >> >maven-jar-plugin >> > >> > >> > >> >test-jar >> > >> > >> > >> > >> > >> > This second artifact is referenced in another sub module as a compile >> > dependency. It works fine for all my development BUT it doesn't work >> when >> > I'm trying to release it. Because the release:prepare goal only executes >> the >> > "clean verify" goals not the install one. >> >> This is a known problem >> http://jira.codehaus.org/browse/MRELEASE-264 >> >> The workaround is to add to your command line >> -DpreparationGoals=clean install >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
Re: Problems with release:prepare on the resolution of a dependency with "test" classifier
The workaround is not working for me! I tried mvn release:prepare -DpreparationGoals="clean install" without success. Any other thoughts?? On Sun, Jan 25, 2009 at 11:44 PM, Barrie Treloar wrote: > On Mon, Jan 26, 2009 at 5:03 PM, Thiago Moreira (timba) > wrote: > > Hi there, > > > > I have a multi module project and one of the sub modules produce two > > artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is built > > using this configuration: > > > > > >maven-jar-plugin > > > > > > > >test-jar > > > > > > > > > > > > This second artifact is referenced in another sub module as a compile > > dependency. It works fine for all my development BUT it doesn't work when > > I'm trying to release it. Because the release:prepare goal only executes > the > > "clean verify" goals not the install one. > > This is a known problem > http://jira.codehaus.org/browse/MRELEASE-264 > > The workaround is to add to your command line > -DpreparationGoals=clean install > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Problems with release:prepare on the resolution of a dependency with "test" classifier
Hi there, I have a multi module project and one of the sub modules produce two artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is built using this configuration: maven-jar-plugin test-jar This second artifact is referenced in another sub module as a compile dependency. It works fine for all my development BUT it doesn't work when I'm trying to release it. Because the release:prepare goal only executes the "clean verify" goals not the install one. I configured the maven-release-plugin on the parent project as: org.apache.maven.plugins maven-release-plugin true clean verify and on the sub module as: org.apache.maven.plugins maven-release-plugin install But still not working. Am I missing something? Cheers
Re: ${pom.version} without the SNAPSHOT part.
Ok, I found the solution!
To add the Eclipse plugins to the Maven repository you should use the
maven-eclipse-plugin for it. The goal is
eclipse:make-artifacts<http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html>
Cheers
On Sun, Jan 25, 2009 at 1:05 PM, Thiago Moreira (timba) <
tmoreira2...@gmail.com> wrote:
>
> Okay, I found the problem!
>
> Eclipse don't accept "-" on the name of the artifacs... so I changed the
> name to 1.2.3.SNAPSHOT and now I'm good to go.
>
> Another question, how can I reference a Eclipse dependency in the pom
> file?? Like org.eclipse.core.resources??
>
> Cheers
>
>
> On Sun, Jan 25, 2009 at 8:44 AM, Rusty Wright wrote:
>
>> If I understand that OSGi version grammar, doesn't that mean that
>> 1.2.3-SNAPSHOT is an invalid OSGi version number? I.e., only periods are
>> allowed between the version parts, no dash, and there should be three
>> periods, not two. E.g., 1.2.3.SNAPSHOT.
>>
>> Does the maven OSGi plugin transform the maven style version number to the
>> OSGi style when creating the bundle/jar?
>>
>> I was reading about OSGi over the winter break and it looks like the
>> answer for various problems.
>>
>>
>>
>> Baptiste MATHUS wrote:
>>
>>> I don't think it is. But I'm not sure I understand what you want to do.
>>> If
>>> you're trying to build an eclipse plugin jar from some project, you
>>> shouldn't do it yourself. There's tools out there that will do it just
>>> fine:
>>> have a look at tycho, maven-bundle-plugin, or maven-pde-plugin (this last
>>> one is quite outdated, from what I remember).
>>>
>>> These tools will deal just fine with your version number.
>>>
>>> Fwiw, here's the OSGi versioning grammar:
>>> version::=major('.'minor('.'micro('.'qualifier)?)?)?
>>> major::=digit+
>>> minor::=digit+
>>> micro::=digit+
>>> qualifier::=(alpha|digit|'_'|'-')+
>>> digit::=[0..9]
>>> alpha::=[a..zA..Z]
>>> There must be no whitespace in version.
>>>
>>> Cheers
>>>
>>> 2009/1/25 Thiago Moreira (timba)
>>>
>>> Hi there,
>>>>
>>>> Is there a way to get only the numbers of the ${pom.version} property??
>>>> Something like this: 1.2.3-SNAPSHOT, I want just the 1.2.3 part.I will
>>>> use
>>>> it to build a Eclipse plugin that don't accept Strings on the version
>>>> property.
>>>>
>>>> Thanks
>>>>
>>>> Thiago Moreira
>>>>
>>>>
>>>
>>>
>>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
Re: ${pom.version} without the SNAPSHOT part.
Okay, I found the problem!
Eclipse don't accept "-" on the name of the artifacs... so I changed the
name to 1.2.3.SNAPSHOT and now I'm good to go.
Another question, how can I reference a Eclipse dependency in the pom
file?? Like org.eclipse.core.resources??
Cheers
On Sun, Jan 25, 2009 at 8:44 AM, Rusty Wright wrote:
> If I understand that OSGi version grammar, doesn't that mean that
> 1.2.3-SNAPSHOT is an invalid OSGi version number? I.e., only periods are
> allowed between the version parts, no dash, and there should be three
> periods, not two. E.g., 1.2.3.SNAPSHOT.
>
> Does the maven OSGi plugin transform the maven style version number to the
> OSGi style when creating the bundle/jar?
>
> I was reading about OSGi over the winter break and it looks like the answer
> for various problems.
>
>
>
> Baptiste MATHUS wrote:
>
>> I don't think it is. But I'm not sure I understand what you want to do. If
>> you're trying to build an eclipse plugin jar from some project, you
>> shouldn't do it yourself. There's tools out there that will do it just
>> fine:
>> have a look at tycho, maven-bundle-plugin, or maven-pde-plugin (this last
>> one is quite outdated, from what I remember).
>>
>> These tools will deal just fine with your version number.
>>
>> Fwiw, here's the OSGi versioning grammar:
>> version::=major('.'minor('.'micro('.'qualifier)?)?)?
>> major::=digit+
>> minor::=digit+
>> micro::=digit+
>> qualifier::=(alpha|digit|'_'|'-')+
>> digit::=[0..9]
>> alpha::=[a..zA..Z]
>> There must be no whitespace in version.
>>
>> Cheers
>>
>> 2009/1/25 Thiago Moreira (timba)
>>
>> Hi there,
>>>
>>> Is there a way to get only the numbers of the ${pom.version} property??
>>> Something like this: 1.2.3-SNAPSHOT, I want just the 1.2.3 part.I will
>>> use
>>> it to build a Eclipse plugin that don't accept Strings on the version
>>> property.
>>>
>>> Thanks
>>>
>>> Thiago Moreira
>>>
>>>
>>
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
${pom.version} without the SNAPSHOT part.
Hi there,
Is there a way to get only the numbers of the ${pom.version} property??
Something like this: 1.2.3-SNAPSHOT, I want just the 1.2.3 part.I will use
it to build a Eclipse plugin that don't accept Strings on the version
property.
Thanks
Thiago Moreira
Re: Site deployment to sourceforge.net broken
I found the following work around to this problem: scp -r target/site/* thiagolm,[EMAIL PROTECTED]:/home/groups/f/fl/floggy/htdocs Until the problem isn't be solved I will update the site using two steps: mvn clean site and then using the scp command. Thiago Moreira On Tue, Oct 7, 2008 at 8:28 AM, Thiago Moreira (timba) < [EMAIL PROTECTED]> wrote: > > Voted! > > > On Tue, Oct 7, 2008 at 4:52 AM, Marat Radchenko < > [EMAIL PROTECTED]> wrote: > >> Done: http://jira.codehaus.org/browse/MDEPLOY-86 >> >> 2008/10/6 Wayne Fay <[EMAIL PROTECTED]>: >> > Then file a bug in JIRA, and get lots of people to vote on it. >> > >> > Complaining about bugs on the Maven Users list is certainly not >> > guaranteed to have them addressed. >> > >> > Wayne >> > >> > On Mon, Oct 6, 2008 at 3:45 AM, Marat Radchenko >> > <[EMAIL PROTECTED]> wrote: >> >> Ping. This is a really serious bug. It affects all sf-hosted maven >> projects. >> >> >> >> 2008/9/25 Marat Radchenko <[EMAIL PROTECTED]>: >> >>> After last changes in sf.net infrastructure there are three ways of >> >>> uploading stuff to web area: >> >>> >> >>> 1) sftp >> >>> 2) scp >> >>> 3) rsync over ssh >> >>> >> >>> I've tried two first options and they both failed. Maven uploads zip >> >>> file (wagon.zip) and then tries to unzip it. However unzip >> >>> commandis not available. >> >>> As far as I understand, Maven doesn't support site deployment via >> rsync. >> >>> >> >>> Am I doing something wrong or it is a real bug? Any existing >> workarounds? >> >>> >> >> >> >> - >> >> 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: Site deployment to sourceforge.net broken
Voted! On Tue, Oct 7, 2008 at 4:52 AM, Marat Radchenko <[EMAIL PROTECTED] > wrote: > Done: http://jira.codehaus.org/browse/MDEPLOY-86 > > 2008/10/6 Wayne Fay <[EMAIL PROTECTED]>: > > Then file a bug in JIRA, and get lots of people to vote on it. > > > > Complaining about bugs on the Maven Users list is certainly not > > guaranteed to have them addressed. > > > > Wayne > > > > On Mon, Oct 6, 2008 at 3:45 AM, Marat Radchenko > > <[EMAIL PROTECTED]> wrote: > >> Ping. This is a really serious bug. It affects all sf-hosted maven > projects. > >> > >> 2008/9/25 Marat Radchenko <[EMAIL PROTECTED]>: > >>> After last changes in sf.net infrastructure there are three ways of > >>> uploading stuff to web area: > >>> > >>> 1) sftp > >>> 2) scp > >>> 3) rsync over ssh > >>> > >>> I've tried two first options and they both failed. Maven uploads zip > >>> file (wagon.zip) and then tries to unzip it. However unzip > >>> commandis not available. > >>> As far as I understand, Maven doesn't support site deployment via > rsync. > >>> > >>> Am I doing something wrong or it is a real bug? Any existing > workarounds? > >>> > >> > >> - > >> 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] > >
Site deployment to sourceforge.net broken
Which JIRA project/component should I open the ticket ?? Thanks Thiago Moreira
Re: Antrun issue
What?
Mick Knutson-4 wrote:
>
> ...
>
> On 8/22/06, thiago <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi,
>>
>> I have a multi-project with severals modules. I was trying to use the
>> assembly plugin to create the final project structure. Unfortunatelly the
>> assembly descriptor does not have all the features that I need to achieve
>> this final structure. So I tried to use the antrun plugin. I could make a
>> set of tasks that builds what I want but unfortunatelly the antrun plugin
>> runs before submodules are built so the tasks doesn't do anything at all
>> and
>> then I end up having to call maven twice ("mvn package" and then "mvn
>> antrun:run").
>> So how can I make the antrun behave like the assembly plugin (that is,
>> to
>> have it ran AFTER the submodules are built)?
>>
>> Regards,
>> Thiago Souza
>> --
>> View this message in context:
>> http://www.nabble.com/Antrun-issue-tf2148246.html#a5932040
>> Sent from the Maven - Users forum at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
>
> ---
> Thanks
>
> DJ MICK
> http://www.djmick.com
> http://www.myspace.com/mickknutson
>
>
--
View this message in context:
http://www.nabble.com/Antrun-issue-tf2148246.html#a5932097
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Antrun issue
Hi,
I have a multi-project with severals modules. I was trying to use the
assembly plugin to create the final project structure. Unfortunatelly the
assembly descriptor does not have all the features that I need to achieve
this final structure. So I tried to use the antrun plugin. I could make a
set of tasks that builds what I want but unfortunatelly the antrun plugin
runs before submodules are built so the tasks doesn't do anything at all and
then I end up having to call maven twice ("mvn package" and then "mvn
antrun:run").
So how can I make the antrun behave like the assembly plugin (that is, to
have it ran AFTER the submodules are built)?
Regards,
Thiago Souza
--
View this message in context:
http://www.nabble.com/Antrun-issue-tf2148246.html#a5932040
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 and AspectJ issue
Hi, Everything is doing fine. No weird behavior with -X enabled, -aspectpath contains the jar with the aspects, this last one is compiled with the aspectj plugin too and aspectjrt.jar is in classpath always. It's just that when surefire:test is ran the aspects codes are completely ignored. I can assure that aspects are being applied cause when "showWeaveInfo" is enabled the aj compiler says so. I can also see the generated code using that eclipse class viewer when no source is attached. Any clue? (getting a little bit desperate here =) ) Kind Regards, Thiago Souza Nick Veys wrote: > > Working for me just like that. Try running w/ -X for debug output and > look for anything odd. Also, you can check target/classesbuilddef.lst > and target/test-classesbuilddef.lst and verify the -aspectpath has > your jar on it. > > On 8/15/06, thiago <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >>I'm trying to get maven to work with aspectj. The aspectj-plugin-maven >> is >> working fine (classes are being woven correctly). But when surefire:test >> runs, the aspects codes are not being ran. Here's my current setup: >> >> >> org.codehaus.mojo >> >> aspectj-maven-plugin >> >> >> >> >> compile >> >> >> >> 1.5 >> >> >> >> >> cortex >> >> >> >> >> cortex-retriever-ops-base >> >> >> >> >> >> >> >> >> >> >> >> Aspects are in this cortex-retriever-ops-base library. Any clue anyone? >> >> Kind Regards, >> Thiago Souza >> -- >> View this message in context: >> http://www.nabble.com/M2-and-AspectJ-issue-tf2110863.html#a5819954 >> Sent from the Maven - Users forum at Nabble.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] > > > -- View this message in context: http://www.nabble.com/M2-and-AspectJ-issue-tf2110863.html#a5823316 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 and AspectJ issue
Hi, I'm trying to get maven to work with aspectj. The aspectj-plugin-maven is working fine (classes are being woven correctly). But when surefire:test runs, the aspects codes are not being ran. Here's my current setup: org.codehaus.mojo aspectj-maven-plugin compile 1.5 cortex cortex-retriever-ops-base Aspects are in this cortex-retriever-ops-base library. Any clue anyone? Kind Regards, Thiago Souza -- View this message in context: http://www.nabble.com/M2-and-AspectJ-issue-tf2110863.html#a5819954 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven is lying to me!
Thanks Jörg Schaible wrote: > > thiago wrote on Tuesday, August 15, 2006 2:27 PM: > >> Milos Kleint-2 wrote: >>> >>> >>> maybe it's not interpreting the location correctly and instead >>> deploys to a local disk? try searching for the server/dev/mavenrepo >>> on your local disk. No idea how to setup this url configuration. On >>> linux the same url would definitely deploy to a local directory at >>> /server/dev/mavenrepo >>> >> >> Hi, >> >> Yeh, you're right, I checked my c:\ and I noticed the directory >> created there =) >> >> Ok, so how do I achieve this? How do I map a repository to a >> network share? > > Use a proper URL! > > file:// defines the file protocol > file://localhost/ is the root adress on your local system > file:/// is the short form of file://localhost/ > file:/server/share/ addresses the "share" of "server" in a Windows > network, which is a convenient form of file://localhost/\\server\share\, > since the path from your local system to the server's share is > \\server\share > > Got it? Any other mixture is a concession to user's habbits and may or may > not be supported by the URL parser of your product/app/browser. > > - Jörg > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven-is-lying-to-me%21-tf2108802.html#a5813804 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven is lying to me!
Milos Kleint-2 wrote: > > > maybe it's not interpreting the location correctly and instead deploys > to a local disk? try searching for the server/dev/mavenrepo on your > local disk. > No idea how to setup this url configuration. On linux the same url would > definitely deploy to a local directory at /server/dev/mavenrepo > Hi, Yeh, you're right, I checked my c:\ and I noticed the directory created there =) Ok, so how do I achieve this? How do I map a repository to a network share? Regards, Thiago Souza -- View this message in context: http://www.nabble.com/Maven-is-lying-to-me%21-tf2108802.html#a5813159 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site:deploy execution
Sorry, as i'm new to maven, I have no idea... Why you replied my question with another question? This should be another post! Sebastien Pennec wrote: > > Hello, > > I've had a problem today with the site:deploy command. > > My project had a parent pom, and 4 sub-modules. A distribution management > element is > present in the parent pom, and not in the sub-modules. > What I wanted to do is execute site:deploy on the parent pom and not have > the site > commande propagated to sub-modules. Is there a way to prevent its > execution? > > Thanks! > > Sébastien > > -- > Sébastien Pennec > [EMAIL PROTECTED] > > Logback: The reliable, generic, fast and flexible logging framework for > Java. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven-is-lying-to-me%21-tf2108802.html#a5813014 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven is lying to me!
Hi, I'm quite new to maven, and i'm having troubles with an intranet repository. I have a similar entry in my pom.xml mavenrepo mavenrepo file:///server/dev/mavenrepo When I run "mvn deploy", maven log shows that the artifact is installed locally AND at the configured intranet repository (it even shows the upload progress). But it's a lie!!! The artifact is not copied to \\server\dev\mavenrepo Any clue anyone? Kind Regards, Thiago Souza -- View this message in context: http://www.nabble.com/Maven-is-lying-to-me%21-tf2108802.html#a5812824 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
