RE: Nexus 1.2.0.3 released
Hi, The recommended way is via a mirror. The Maven book walks you through it at [1] and there's a short video at [2]. If you need extra assistance, we are on #nexus on irc.codehaus.org and have a user list at nexus-u...@sonatype.org [1] http://books.sonatype.com/maven-book/reference/repository-manager.html [2] http://vimeo.com/1875558?pg=embed&sec=1875558 --Brian -Original Message- From: Durbha, Praveen (GE Healthcare) [mailto:praveen.dur...@ge.com] Sent: Monday, January 12, 2009 6:04 PM To: Maven Users List Subject: RE: Nexus 1.2.0.3 released How can I configure this in my pom.xml file? Via a proxy? Thanks! -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Monday, January 12, 2009 6:38 PM To: Maven Users List Subject: RE: Nexus 1.2.0.3 released Whoops, wrong user list. From: Brian E. Fox Sent: Monday, January 12, 2009 4:37 PM To: users@maven.apache.org Subject: Nexus 1.2.0.3 released Nexus 1.2.0.3 is now available for release. This is primarily a bug fix release: Release Notes - Open Source Nexus - Version 1.2.0.3 ** Bug * [NEXUS-1195] - On fresh install, Nexus Deployment Role has a single priv, which is Nexus Anonymous Role * [NEXUS-1203] - Nexus is not RFC 2616 compliant * [NEXUS-1252] - Weekly task shows as Monthly from 1.0 to 1.2 upgrade * [NEXUS-1275] - Problem to download plugins when a proxied repository is down * [NEXUS-1298] - no validation on roles with spaces in the id (ui) * [NEXUS-1299] - no validation on roles with spaces in the id (server) * [NEXUS-1300] - Plexus Roles and Plexus Users, bad compareTo method * [NEXUS-1313] - remove heapdump option from the wrapper.conf * [NEXUS-1321] - User locators are not exposed via rest * [NEXUS-1325] - The enviroment variables and system property variables are not overriding those in plexus.properties, but they should * [NEXUS-1337] - While modifiying the edition text, inadvertantly changed the user agent string * [NEXUS-1343] - Adding repos to group, dropping repo on selected panel isn't working properly ** User Story * [NEXUS-1297] - Improve logging of security issues Grab your copy from http://nexus.sonatype.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Nexus 1.2.0.3 released
How can I configure this in my pom.xml file? Via a proxy? Thanks! -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Monday, January 12, 2009 6:38 PM To: Maven Users List Subject: RE: Nexus 1.2.0.3 released Whoops, wrong user list. From: Brian E. Fox Sent: Monday, January 12, 2009 4:37 PM To: users@maven.apache.org Subject: Nexus 1.2.0.3 released Nexus 1.2.0.3 is now available for release. This is primarily a bug fix release: Release Notes - Open Source Nexus - Version 1.2.0.3 ** Bug * [NEXUS-1195] - On fresh install, Nexus Deployment Role has a single priv, which is Nexus Anonymous Role * [NEXUS-1203] - Nexus is not RFC 2616 compliant * [NEXUS-1252] - Weekly task shows as Monthly from 1.0 to 1.2 upgrade * [NEXUS-1275] - Problem to download plugins when a proxied repository is down * [NEXUS-1298] - no validation on roles with spaces in the id (ui) * [NEXUS-1299] - no validation on roles with spaces in the id (server) * [NEXUS-1300] - Plexus Roles and Plexus Users, bad compareTo method * [NEXUS-1313] - remove heapdump option from the wrapper.conf * [NEXUS-1321] - User locators are not exposed via rest * [NEXUS-1325] - The enviroment variables and system property variables are not overriding those in plexus.properties, but they should * [NEXUS-1337] - While modifiying the edition text, inadvertantly changed the user agent string * [NEXUS-1343] - Adding repos to group, dropping repo on selected panel isn't working properly ** User Story * [NEXUS-1297] - Improve logging of security issues Grab your copy from http://nexus.sonatype.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Nexus 1.2.0.3 released
Whoops, wrong user list. From: Brian E. Fox Sent: Monday, January 12, 2009 4:37 PM To: users@maven.apache.org Subject: Nexus 1.2.0.3 released Nexus 1.2.0.3 is now available for release. This is primarily a bug fix release: Release Notes - Open Source Nexus - Version 1.2.0.3 ** Bug * [NEXUS-1195] - On fresh install, Nexus Deployment Role has a single priv, which is Nexus Anonymous Role * [NEXUS-1203] - Nexus is not RFC 2616 compliant * [NEXUS-1252] - Weekly task shows as Monthly from 1.0 to 1.2 upgrade * [NEXUS-1275] - Problem to download plugins when a proxied repository is down * [NEXUS-1298] - no validation on roles with spaces in the id (ui) * [NEXUS-1299] - no validation on roles with spaces in the id (server) * [NEXUS-1300] - Plexus Roles and Plexus Users, bad compareTo method * [NEXUS-1313] - remove heapdump option from the wrapper.conf * [NEXUS-1321] - User locators are not exposed via rest * [NEXUS-1325] - The enviroment variables and system property variables are not overriding those in plexus.properties, but they should * [NEXUS-1337] - While modifiying the edition text, inadvertantly changed the user agent string * [NEXUS-1343] - Adding repos to group, dropping repo on selected panel isn't working properly ** User Story * [NEXUS-1297] - Improve logging of security issues Grab your copy from http://nexus.sonatype.org
Nexus 1.2.0.3 released
Nexus 1.2.0.3 is now available for release. This is primarily a bug fix release: Release Notes - Open Source Nexus - Version 1.2.0.3 ** Bug * [NEXUS-1195] - On fresh install, Nexus Deployment Role has a single priv, which is Nexus Anonymous Role * [NEXUS-1203] - Nexus is not RFC 2616 compliant * [NEXUS-1252] - Weekly task shows as Monthly from 1.0 to 1.2 upgrade * [NEXUS-1275] - Problem to download plugins when a proxied repository is down * [NEXUS-1298] - no validation on roles with spaces in the id (ui) * [NEXUS-1299] - no validation on roles with spaces in the id (server) * [NEXUS-1300] - Plexus Roles and Plexus Users, bad compareTo method * [NEXUS-1313] - remove heapdump option from the wrapper.conf * [NEXUS-1321] - User locators are not exposed via rest * [NEXUS-1325] - The enviroment variables and system property variables are not overriding those in plexus.properties, but they should * [NEXUS-1337] - While modifiying the edition text, inadvertantly changed the user agent string * [NEXUS-1343] - Adding repos to group, dropping repo on selected panel isn't working properly ** User Story * [NEXUS-1297] - Improve logging of security issues Grab your copy from http://nexus.sonatype.org
[ANN] Maven Stylus Skin 1.1 Released
The Maven team is pleased to announce the release of the Maven Site Skin, version 1.1 http://maven.apache.org/skins/maven-stylus-skin You should specify the version in your site.xml: ... org.apache.maven.skins maven-stylus-skin 1.1 ... Release Notes - Maven Skins - Version stylus-1.1 ** Task * [MSKINS-5] - Adds a privacy policy link as required by the board Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Qualifier
Sorry, Wendy, but I doesn't know, that qualifier is used only for remote repository. Wendy Smoak-3 wrote: > > On Mon, Jan 12, 2009 at 10:36 AM, buters wrote: >> Example: >> Is: foo-3.0-SNAPSHOT.jar >> Should be: foo-3.0-20090110.064228-1.jar > > I assume you are looking in your remote repository? This is normal. > > You're seeing a timestamped snapshot. This is the default naming > convention for snapshots in the remote repo - it's > artifactId-version-date-time-buildnumber.packaging. > > You can turn it off by setting false in > distributionManagement for that repository, and then it will just keep > overwriting the one foo-3.0-SNAPSHOT.jar file. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Qualifier-tp21414940p21425169.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: Mvn eclipse:eclipse - strange M2_REPO settings
On Mon, Jan 12, 2009 at 9:32 PM, crowne wrote: > > I am experiencing this too, and I found a jira for this issue which was > closed but I think should be reopened. > http://jira.codehaus.org/browse/MECLIPSE-408 I've re-opened it. I haven't had the chance to look in detail at the problem. If there are enough steps to reproduce the problem then there is a better chance of it getting fixed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Qualifier
On Mon, Jan 12, 2009 at 10:36 AM, buters wrote: > Example: > Ist: foo-3.0-SNAPSHOT.jar > Soll: foo-3.0-20090110.064228-1.jar I assume you are looking in your remote repository? This is normal. You're seeing a timestamped snapshot. This is the default naming convention for snapshots in the remote repo - it's artifactId-version-date-time-buildnumber.packaging. You can turn it off by setting false in distributionManagement for that repository, and then it will just keep overwriting the one foo-3.0-SNAPSHOT.jar file. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Qualifier
Example: Ist: foo-3.0-SNAPSHOT.jar Soll: foo-3.0-20090110.064228-1.jar Wendy Smoak-3 wrote: > > On Mon, Jan 12, 2009 at 7:00 AM, buters wrote: > >> what can I do, that after a build of my snapshot the artifact is named >> "version-qualifier.jar" instead of "version-snapshot.jar" > > An example would help here... where are you looking, and what is the > actual filename vs. the one you expected? > > I'm guessing that you might be looking at a timestamped snapshot, but > it isn't clear. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Qualifier-tp21414940p21419438.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: unable to set repo loc using maven release plugin 2.0-beta-8
Even I faced similar issue while using release-plugin. Since I do parallel builds, I can't rely on ~/.m2/repository for all my builds, so I must different local repo. Any help is appreciated. Thanks, Sahoo Jane Young wrote: Hi Release Plugin Gurus, I want to specify a local maven repo. Using maven release plugin 2.0-beta-8, I tried the combinations of "-Darguments=-Dmaven.repo.local=...", "-Darguments=-Dmaven.home...", -DlocalRepoDirectory=..." and/or "-DmavenHome=...", it always return /.m2/repository not found. Is this a known issue? Is there a workaround? This was working in 2.0-beta-7. However, in the 2.0-beta-7 release, the parameters releaseVersion and developmentVersion are not working. See: http://jira.codehaus.org/browse/MRELEASE-389 Thanks, Jane - 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: war dependency not being picked up?
thank you Wendy, that's wonderful :) for anyone else wanting to do this, here's what I did: I went for the second option. details on both are on the maven-war-plugin's FAQ. it's the second part here: http://maven.apache.org/plugins/maven-war-plugin/faq.html#attached this only works in the development version of the war plugin (until 2.1 is released), so add the following to your tag: snapshots http://people.apache.org/repo/m2-snapshot-repository/ then you can use version 2.1-beta-1-SNAPSHOT of the war plugin. now when you run the maven build, you get a jar and a war installed to your repository. but as the jar file has -classes appended to the filename, you need to tell maven this by adding: classes to the tag you need. thanks again B Wendy Smoak-3 wrote: > > On Mon, Jan 12, 2009 at 6:37 AM, Ben Avery wrote: > > >> so I have created a functional-testing module, which contains the tests, >> but >> the tests have dependencies on classes in the other modules. I have >> listed >> the [war] modules as dependencies of the funtional test pom, but the >> compile phase >> fails, as it can't see these classes. if I rig the build to compile the >> modules as jars instead, the compilation succeeds (but obviously the >> tests >> can't run, as I need wars to be deployed). > > This is expected. Java has no concept of a war file on the classpath. > (It expects the directory structure to start at the root of the file, > it doesn't know to look down under WEB-INF/classes.) > > A couple of options > - move the classes out to a separate module and build a jar from > that, which would then be a "normal" dependency for both the war and > the tests, or > - configure the war plugin to 'attach' the classes as a jar artifact > in addition to the war, so you can depend on the jar from other > projects. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/war-dependency-not-being-picked-up--tp21414576p21419364.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
Question about component descriptors and reuse
With the advice I've seen from you all, I've been working on learning how to better decouple my builds by bundling resources and then sharing them out with projects, and void the tendency to want to include paths between dependencies, which can lead to broken builds. This leads me to a question that I haven't seen an answer to (I'm not sure if it's there staring me in the face and I'm not noticing). If you have a component descriptor that you want to share amoung multiple projects that may be located in various locations in your source tree and potentially not having the same parent, how do you recommend doing it? Basically, I have a distribution project that creates a distribution and uses a common component descriptor. I want other projects that make special derivatives of that distribution to also use that component descriptor, but I'm not sure how you would share it? Are there any best practices for that. The component descriptors don't get bundled into an artifact right? Do you make a special artifact for them? Thanks for any help! Ryan
Implicitly defined anchors
The APT reference in the Doxia documentation says:
"Section titles are implicitly defined anchors."
I assume this means I can create an anchor link to a section without
having to explicitly define an anchor for that section.
I've tried to use this feature by putting the name of a top-level
section between double curly braces (e.g., {{Installation}}), and it
does create an anchor link in the HTML (e.g., href="#Installation">), but it doesn't go anywhere. There's no
corresponding anchor in the HTML (e.g., ).
It all works as expected if I explicitly make an anchor out of the
section title.
Is this a bug, or have I misunderstood the documentation? Thanks,
Trevor
Re: release plugin only works with snapshot projects.
You can always write your own release plugin... most of the primitives needed are in a separate module and the maven-release-plugin is just a thin wrapper on top. -Stephen 2009/1/12 Tibor Kiss > Thank You! > > I asked because I would like to match with our current development > aproaches. Maybe it worst looking into detail, because here are working > subcontractors and only module managers are deploying. The separation of > workspace is realised by SVN authorization on different branches. > > Usually we are working in at least two branches. One of the branches plays > the role of integration and user acceptance test branch (UAT) and at least > one development branch (DEV_*) (the number of DEV_ branches depends on the > number of parallel works). This is because the writing permission on UAT is > given only to module managers! (The development teams usually are different > subcontractors, so they are working on their own DEV_* or BUGFIX_* > branches.) > > The ideea is that merging into UAT is performed only by module managers. > But before the DEV team is passing the merging task to module manager, they > synchronizes with the UAT content (merge from UAT to DEV_) to be in synchron > state. In this way the DEV_ team has the same sources as on the stable UAT > plus what they modified. After the development tests (on DEV_ branch) > passes, everything goes to acceptance tests by merging into UAT and > releasing it as a staging version. If any errors occurs on user acceptance > test environment, they will be fixed on DEV_* branches then updated + merged > to UAT. Every new release is getting a diferent version, so is no version > overwriting in maven repository. > > In UAT environment instead of using 1.1.1-SNAPSHOT version we would use > 1.1.1-01 (..-) > becauses the policy is that on UAT servers is not allowed to install > developer version. "01" means and always is changing with every > deployment on UAT environment. At one point a version is passing user > acceptance tests and that version goes to PRODUCTION. we are > incrementing when incompatible changes are introduced and version> is bound to a feature set. > > It seems that the source codes on UAT branch and the DEV_ branches must be > versioned with SNAPSHOT and the release:prepare (and :perform) commands has > to be used only on UAT branch by modul managers. Therefore form UAT branch > is useless to deploy a snapshot. Usually it's enough to use release plugin > to build releases. > > Another issue is that often we have different teams working with > applications which are interdependent and goes to UAT tests together (not > enough timeframe each individually be tested on uat env.). That means, they > will have on their dependencyManagement some SNAPSHOT dependencies which > needs to be resolved manually before releasing it. Until now I was thinking > that version range dependencies without -SNAPSHOT would be enough for us, > but won't be enough. I'm right? > But what about a two parallel development branch who wouldn't want to see > each other's on dependencies? They will use non overlapping version ranges > or all their dependencies (also SNAPSHOT) will be fixed? > > Sorry for too much details. Right now I am facing these real condition > issues which differs a little bit compared to open source aproach. > > Regards, > Tibor > > Feladó: Stephen Connolly [stephen.alan.conno...@gmail.com] > Küldve: 2009. január 12. 14:27 > Címzett: Maven Users List > Tárgy: Re: release plugin only works with snapshot projects. > > Functions as designed. > > You should only ever do development work on a project that has a -SNAPSHOT > version. > > The -SNAPSHOT version indicates that this is the version we are working > towards... > > Maven does not allow re-deploying a non-SNAPSHOT version, so that if you > are > doing development with a pom that has version 4.5.1 and somebody > accidentally runs > > mvn deploy > > Then the code base *at that specific point in time* is what will be > deployed. > > When you then later try to deploy 4.5.1 for real, the redeployment will/may > be silently quashed (depending on what repository manager and what version > of the maven deploy plugin you are using) and you have an irreproducible > build. > > So the short answer is: "Because you'll f*ck it up if you don't use a > -SNAPSHOT version" > > -Stephen > > 2009/1/12 Tibor Kiss > > > Hi. > > > > If I try to prepare a multi-project whose version is a non-snapshot > > version, it throws an exception: > > "You don't have a SNAPSHOT project in the reactor projects list." > > > > I don't understand why is a must to start releasing from a snapshot > > version? > > > > Regards, > > Tibor > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > -
RE: release plugin only works with snapshot projects.
Thank You! I asked because I would like to match with our current development aproaches. Maybe it worst looking into detail, because here are working subcontractors and only module managers are deploying. The separation of workspace is realised by SVN authorization on different branches. Usually we are working in at least two branches. One of the branches plays the role of integration and user acceptance test branch (UAT) and at least one development branch (DEV_*) (the number of DEV_ branches depends on the number of parallel works). This is because the writing permission on UAT is given only to module managers! (The development teams usually are different subcontractors, so they are working on their own DEV_* or BUGFIX_* branches.) The ideea is that merging into UAT is performed only by module managers. But before the DEV team is passing the merging task to module manager, they synchronizes with the UAT content (merge from UAT to DEV_) to be in synchron state. In this way the DEV_ team has the same sources as on the stable UAT plus what they modified. After the development tests (on DEV_ branch) passes, everything goes to acceptance tests by merging into UAT and releasing it as a staging version. If any errors occurs on user acceptance test environment, they will be fixed on DEV_* branches then updated + merged to UAT. Every new release is getting a diferent version, so is no version overwriting in maven repository. In UAT environment instead of using 1.1.1-SNAPSHOT version we would use 1.1.1-01 (..-) becauses the policy is that on UAT servers is not allowed to install developer version. "01" means and always is changing with every deployment on UAT environment. At one point a version is passing user acceptance tests and that version goes to PRODUCTION. we are incrementing when incompatible changes are introduced and is bound to a feature set. It seems that the source codes on UAT branch and the DEV_ branches must be versioned with SNAPSHOT and the release:prepare (and :perform) commands has to be used only on UAT branch by modul managers. Therefore form UAT branch is useless to deploy a snapshot. Usually it's enough to use release plugin to build releases. Another issue is that often we have different teams working with applications which are interdependent and goes to UAT tests together (not enough timeframe each individually be tested on uat env.). That means, they will have on their dependencyManagement some SNAPSHOT dependencies which needs to be resolved manually before releasing it. Until now I was thinking that version range dependencies without -SNAPSHOT would be enough for us, but won't be enough. I'm right? But what about a two parallel development branch who wouldn't want to see each other's on dependencies? They will use non overlapping version ranges or all their dependencies (also SNAPSHOT) will be fixed? Sorry for too much details. Right now I am facing these real condition issues which differs a little bit compared to open source aproach. Regards, Tibor Feladó: Stephen Connolly [stephen.alan.conno...@gmail.com] Küldve: 2009. január 12. 14:27 Címzett: Maven Users List Tárgy: Re: release plugin only works with snapshot projects. Functions as designed. You should only ever do development work on a project that has a -SNAPSHOT version. The -SNAPSHOT version indicates that this is the version we are working towards... Maven does not allow re-deploying a non-SNAPSHOT version, so that if you are doing development with a pom that has version 4.5.1 and somebody accidentally runs mvn deploy Then the code base *at that specific point in time* is what will be deployed. When you then later try to deploy 4.5.1 for real, the redeployment will/may be silently quashed (depending on what repository manager and what version of the maven deploy plugin you are using) and you have an irreproducible build. So the short answer is: "Because you'll f*ck it up if you don't use a -SNAPSHOT version" -Stephen 2009/1/12 Tibor Kiss > Hi. > > If I try to prepare a multi-project whose version is a non-snapshot > version, it throws an exception: > "You don't have a SNAPSHOT project in the reactor projects list." > > I don't understand why is a must to start releasing from a snapshot > version? > > Regards, > Tibor > - > 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
Project documentation (with Doxia)
I'm getting started with Doxia but have run into some issues. 1) "mvn site" converts my APT files to HTML, but I want them converted to PDF as well. I know PDF generation is possible with the "aptconvert" utility, but how can I do it with Maven, preferably as part of the site phase? 2) Many of the figures referenced by my APT file are authored in some proprietary format (e.g. UML illustrations), then they're converted into PNG and placed into src/site/resources/images so that they can be accessed by the generated HTML. But where do I store the original files? Should I just place them alongside the PNG files in the images directory, even though that will copy them into the site's target directory for no reason? 3) What if I have documentation that doesn't really belong in the project web site? For instance, we've got an Adobe Illustrator document for printing a high-quality PDF user guide. Is there a Maven convention on where it belongs? (Maven's standard directory layout only addresses developer-facing files and doesn't mention anything about end-user documentation.) Thanks, Trevor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Older Versions of m2eclipse
Christian, We don't delete previous versions from the release update site and you should be able to install them from there (e.g. unselect "show only last version" checkbox in the update manager UI). You can also try the dev build that should fix for the most of MNGECLIPSE-983. The update site is at http://m2eclipse.sonatype.org/update-dev/ regards, Eugene Christian Kalkhoff-3 wrote: > > Hi, > > I cannot see the source of workspace projects in eclipse due bug > http://jira.codehaus.org/browse/MNGECLIPSE-983 > . It will get fixed in 0.9.8 but I need a workaround till then. Is > it possible to install historic versions (I guess the problem stepped > in 0.9.6) of m2eclipse? Where can I find older builds? Or do I have to > build them on my own? > > Regards. > > Christian Kalkhoff > -- View this message in context: http://www.nabble.com/Older-Versions-of-m2eclipse-tp21413616p21417010.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: Block level elements do not appear in output
Trevor Harmon wrote: On Jan 12, 2009, at 9:31 AM, Lukas Theussl wrote: The information is there but as meta information, it's not content- information. Eg the maven site has 100s of documents written by different people at different times, you don't want to see all that when you browse the site, do you? I'm not sure what you mean by "all that". There are only three pieces of information: title, author, and date. I would definitely want to see these important attributes when reading the documentation about something. The purpose of adding it is to record some information about the origin of the document, not to convey information for the end-user. I disagree about that. Recording the origin and history of the document is already handled by the source code repository. There's no sense in duplicating that information in the APT file, unless the goal is to make it readily visible to the reader... but it's not, hence my confusion. Looking at this another way... If you just want to include some "invisible" metadata, you can always insert it into the APT file as a comment. Any non-comments in the APT file should be visible to the reader, since that was likely the author's intent. I don't quite see the point of this discussion anymore... let's just take it as a definition: the default doxia xhtml sink treats title date and author as meta information. If you want it to behave differently then write and use your own Sink (I'll gladly review any patches! :) ). If you want title/date/author to appear on your site for every single page then include it as content. So everyone can be made happy... -Lukas Trevor
Re: war dependency not being picked up?
On Mon, Jan 12, 2009 at 6:37 AM, Ben Avery wrote: > so I have created a functional-testing module, which contains the tests, but > the tests have dependencies on classes in the other modules. I have listed > the [war] modules as dependencies of the funtional test pom, but the compile > phase > fails, as it can't see these classes. if I rig the build to compile the > modules as jars instead, the compilation succeeds (but obviously the tests > can't run, as I need wars to be deployed). This is expected. Java has no concept of a war file on the classpath. (It expects the directory structure to start at the root of the file, it doesn't know to look down under WEB-INF/classes.) A couple of options - move the classes out to a separate module and build a jar from that, which would then be a "normal" dependency for both the war and the tests, or - configure the war plugin to 'attach' the classes as a jar artifact in addition to the war, so you can depend on the jar from other projects. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
Now I have, thank you very much! -Original Message- From: Nicolas Dordet [mailto:dorde...@gmail.com] Sent: maandag 12 januari 2009 16:16 To: Maven Users List Subject: Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ Have you configure the file settings.xml for your proxy ? http://maven.apache.org/guides/mini/guide-proxies.html 2009/1/12 > > Thanks for the fast reply. > > archetype:generate doesn't work either. > This is my output: > > > C:\Documents and Settings\sverfail>mvn archetype:generate > -DgroupId=com.roularta .app -DartifactId=my-app [INFO] Scanning for > projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could > not be retri eved from repository: central due to an error: Error > transferring file [INFO] Repository 'central' will be blacklisted > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > -- > -- [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' > does not exi st or no valid version could be found [INFO] > -- > -- [INFO] For more information, run Maven with the -e switch [INFO] > -- > -- > [INFO] Total time: 21 seconds > [INFO] Finished at: Mon Jan 12 16:05:43 CET 2009 [INFO] Final Memory: > 1M/4M [INFO] > -- > -- > > > Yes, I use a proxy: httpproxy.rmg.be > > Do you know anything more with this? > > > > -Original Message- > From: Nicolas Dordet [mailto:dorde...@gmail.com] > Sent: maandag 12 januari 2009 16:04 > To: Maven Users List > Subject: Re: maven-archetype-plugin does not exist error when creating > new project, non-working link in FAQ > > No problem for me to lauch this goal (mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e) on maven 2.0.9. > > But first of all, maven say : "This goal is deprecated. Please use mvn > archetype:generate instead" > > Are you using a proxy? > > > 2009/1/12 > > > Hello, > > > > When I try to create a new projects with my new installed maven, I > > get > > > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: > > the > > > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not > > exist or no valid version could be found. > > > > I used this syntax to create it: mvn archetype:create > > -DgroupId=com.roularta.app -DartifactId=my-app -e > > > > All the environment vars are ok. > > > > I see this exact error named in the FAQ, but the link to the answer > > doesn't work/exist.. > > > > Does anybody know what exactly goes wrong? > > > > Thanks for the effort. > > > > Kind regards, > > Sandy > > > > > > - > 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: Qualifier
On Mon, Jan 12, 2009 at 7:00 AM, buters wrote: > what can I do, that after a build of my snapshot the artifact is named > "version-qualifier.jar" instead of "version-snapshot.jar" An example would help here... where are you looking, and what is the actual filename vs. the one you expected? I'm guessing that you might be looking at a timestamped snapshot, but it isn't clear. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
oh crap, ofcourse :) I searched for the previous question and then read the question after it, but that didn't 'work'. Thank you very much, my project is created! Regards, Sandy -Original Message- From: Martin Höller [mailto:mar...@xss.co.at] Sent: maandag 12 januari 2009 16:16 To: Maven Users List Subject: Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ On Monday 12 January 2009 sandy.verfai...@roularta.be wrote: > Hello, > > When I try to create a new projects with my new installed maven, I get > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found. > > I used this syntax to create it: mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e > > All the environment vars are ok. > > I see this exact error named in the FAQ, but the link to the answer > doesn't work/exist.. The answer can be found on the same page. Just search for "How do I resolve" and you'll get the answer. I just tried to update the wiki-page, but I always get a "page not found" error :-( hth, - martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
On Monday 12 January 2009 Martin Höller wrote: > I just tried to update the wiki-page, but I always get a "page not found" > error :-( This seems to be a problem with konqueror. Updateing in firefox worked. - martin signature.asc Description: This is a digitally signed message part.
Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
Have you configure the file settings.xml for your proxy ? http://maven.apache.org/guides/mini/guide-proxies.html 2009/1/12 > > Thanks for the fast reply. > > archetype:generate doesn't work either. > This is my output: > > > C:\Documents and Settings\sverfail>mvn archetype:generate > -DgroupId=com.roularta > .app -DartifactId=my-app > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not > be retri > eved from repository: central due to an error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does > not exi > st or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 21 seconds > [INFO] Finished at: Mon Jan 12 16:05:43 CET 2009 > [INFO] Final Memory: 1M/4M > [INFO] > > > > Yes, I use a proxy: httpproxy.rmg.be > > Do you know anything more with this? > > > > -Original Message- > From: Nicolas Dordet [mailto:dorde...@gmail.com] > Sent: maandag 12 januari 2009 16:04 > To: Maven Users List > Subject: Re: maven-archetype-plugin does not exist error when creating > new project, non-working link in FAQ > > No problem for me to lauch this goal (mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e) on maven 2.0.9. > > But first of all, maven say : "This goal is deprecated. Please use mvn > archetype:generate instead" > > Are you using a proxy? > > > 2009/1/12 > > > Hello, > > > > When I try to create a new projects with my new installed maven, I get > > > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the > > > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not > > exist or no valid version could be found. > > > > I used this syntax to create it: mvn archetype:create > > -DgroupId=com.roularta.app -DartifactId=my-app -e > > > > All the environment vars are ok. > > > > I see this exact error named in the FAQ, but the link to the answer > > doesn't work/exist.. > > > > Does anybody know what exactly goes wrong? > > > > Thanks for the effort. > > > > Kind regards, > > Sandy > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
On Monday 12 January 2009 sandy.verfai...@roularta.be wrote: > Hello, > > When I try to create a new projects with my new installed maven, I get > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not exist > or no valid version could be found. > > I used this syntax to create it: mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e > > All the environment vars are ok. > > I see this exact error named in the FAQ, but the link to the answer > doesn't work/exist.. The answer can be found on the same page. Just search for "How do I resolve" and you'll get the answer. I just tried to update the wiki-page, but I always get a "page not found" error :-( hth, - martin signature.asc Description: This is a digitally signed message part.
RE: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
Thanks for the fast reply. archetype:generate doesn't work either. This is my output: C:\Documents and Settings\sverfail>mvn archetype:generate -DgroupId=com.roularta .app -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 21 seconds [INFO] Finished at: Mon Jan 12 16:05:43 CET 2009 [INFO] Final Memory: 1M/4M [INFO] Yes, I use a proxy: httpproxy.rmg.be Do you know anything more with this? -Original Message- From: Nicolas Dordet [mailto:dorde...@gmail.com] Sent: maandag 12 januari 2009 16:04 To: Maven Users List Subject: Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ No problem for me to lauch this goal (mvn archetype:create -DgroupId=com.roularta.app -DartifactId=my-app -e) on maven 2.0.9. But first of all, maven say : "This goal is deprecated. Please use mvn archetype:generate instead" Are you using a proxy? 2009/1/12 > Hello, > > When I try to create a new projects with my new installed maven, I get > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found. > > I used this syntax to create it: mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e > > All the environment vars are ok. > > I see this exact error named in the FAQ, but the link to the answer > doesn't work/exist.. > > Does anybody know what exactly goes wrong? > > Thanks for the effort. > > Kind regards, > Sandy > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
No problem for me to lauch this goal (mvn archetype:create -DgroupId=com.roularta.app -DartifactId=my-app -e) on maven 2.0.9. But first of all, maven say : "This goal is deprecated. Please use mvn archetype:generate instead" Are you using a proxy? 2009/1/12 > Hello, > > When I try to create a new projects with my new installed maven, I get > the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the > plugin "org.apache.maven.plugins:maven-archetype-plugin' does not exist > or no valid version could be found. > > I used this syntax to create it: mvn archetype:create > -DgroupId=com.roularta.app -DartifactId=my-app -e > > All the environment vars are ok. > > I see this exact error named in the FAQ, but the link to the answer > doesn't work/exist.. > > Does anybody know what exactly goes wrong? > > Thanks for the effort. > > Kind regards, > Sandy > >
maven-archetype-plugin does not exist error when creating new project, non-working link in FAQ
Hello, When I try to create a new projects with my new installed maven, I get the error 'org.apache.maven/lifecycle.LifecycleExecutionException: the plugin "org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found. I used this syntax to create it: mvn archetype:create -DgroupId=com.roularta.app -DartifactId=my-app -e All the environment vars are ok. I see this exact error named in the FAQ, but the link to the answer doesn't work/exist.. Does anybody know what exactly goes wrong? Thanks for the effort. Kind regards, Sandy
Re: Block level elements do not appear in output
On Jan 12, 2009, at 8:14 AM, Lukas Theussl wrote: You use 'mvn site' to generate apt files from apt source files? I guess you mean html? In this case the title and author end up in the html , so you don't see them when you view the file with a browser. Yes, sorry, I meant that I'm generating from APT, not to APT. It's odd that the generator puts the title and author into the HTML but makes them invisible. And it ignores the date completely. Doesn't that defeat the purpose of adding this information? Trevor
Qualifier
Hi, what can I do, that after a build of my snapshot the artifact is named "version-qualifier.jar" instead of "version-snapshot.jar" Thanks beforehand, Best regards. -- View this message in context: http://www.nabble.com/Qualifier-tp21414940p21414940.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: Cannot compile simple code
That fixed it.
Thank you!
Brett Randall-2 wrote:
>
> The missing symbol method was added in Java 1.5. Maven defaults to source
> level 1.4. Set your source/target to a minimum of 1.5 on the
> maven-compiler-plugin, see
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html.
>
> Brett
>
> On Mon, Jan 12, 2009 at 10:11 PM, SamadLotia
> wrote:
>
>>
>> Hello fellow Maven users,
>> I have been trying to compile an OSGi project created using the PAX
>> scripts.
>> In the source file ConsoleTaskManager.java on line 15 I have written:
>>
>> System.out.println(java.lang.String.format("%s", "Why will not this
>> compile?"));
>>
>> When I type "mvn install", I get the following error message:
>>
>> [INFO] [pax:compile]
>> [INFO] Compiling 5 source files to
>> /Users/slotia/src/csplugins-slotia/work-pir-api/target/classes
>> [INFO] [recovering meta-data]
>> [INFO]
>>
>> [ERROR] BUILD FAILURE
>> [INFO]
>>
>> [INFO] Compilation failure
>>
>> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
>> cannot find symbol
>> symbol : method format(java.lang.String,java.lang.String)
>> location: class java.lang.String
>>
>>
>> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
>> cannot find symbol
>> symbol : method format(java.lang.String,java.lang.String)
>> location: class java.lang.String
>>
>> If I uncomment the offending line, the project compiles fine. I also
>> wrote
>> a
>> 5-line class file with the offending line, and it compiles fine with
>> javac.
>> This suggests that there probably isn't a problem with the JDK. I have
>> tried
>> to clean the project, which deletes the target directory, delete the
>> runner
>> directory, and delete the .m2 directory, but it still does not compile.
>>
>> Here are some specs of my system:
>> OS: Mac OS X 10.5.6
>> Java: 1.5.0_16-b06-284 32-bit
>> Maven: 2.0.9
>>
>> I am completely lost as to how to fix this. Any help would be greatly
>> appreciated. Thank you.
>> --
>> View this message in context:
>> http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412538.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
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21414859.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
war dependency not being picked up?
hi all, I've searched, but can't see a suitable answer. apols if I've missed one. I have a project which has two modules which compile with war packaging, and I need to perform integration testing using both these wars. the project contains a web service and WS client on both sides, I need to functionally test this, deploying the wars using the Cargo plugin. so I have created a functional-testing module, which contains the tests, but the tests have dependencies on classes in the other modules. I have listed the modules as dependencies of the funtional test pom, but the compile phase fails, as it can't see these classes. if I rig the build to compile the modules as jars instead, the compilation succeeds (but obviously the tests can't run, as I need wars to be deployed). I've checked that the first module is compiling to a war, with the right names and version numbers, etc, and that the classes needed are contained in WEB-INF/classes. I've seen the maven-dependency-plugin mentioned as a solution to this, not how to do this. what goal would do what I need? Would it be better to leave the test classes in the modules that compile to wars, exclude them from that module's surfire configuration, and have the functional test module contain no code itself, but just call these test classes? and would this work, or would they also not be able to see the test classes? any help would be much appreciated. snippet of the start of one of the modules which compiles to a war: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 org.blah.blah blahWar 1.0.1-Continuous war and the functional test pom: 4.0.0 functional-tests pom functional tests ... ... org.blah.blah blahWar 1.0.1-Continuous war -- View this message in context: http://www.nabble.com/war-dependency-not-being-picked-up--tp21414576p21414576.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 plugin only works with snapshot projects.
Functions as designed. You should only ever do development work on a project that has a -SNAPSHOT version. The -SNAPSHOT version indicates that this is the version we are working towards... Maven does not allow re-deploying a non-SNAPSHOT version, so that if you are doing development with a pom that has version 4.5.1 and somebody accidentally runs mvn deploy Then the code base *at that specific point in time* is what will be deployed. When you then later try to deploy 4.5.1 for real, the redeployment will/may be silently quashed (depending on what repository manager and what version of the maven deploy plugin you are using) and you have an irreproducible build. So the short answer is: "Because you'll f*ck it up if you don't use a -SNAPSHOT version" -Stephen 2009/1/12 Tibor Kiss > Hi. > > If I try to prepare a multi-project whose version is a non-snapshot > version, it throws an exception: > "You don't have a SNAPSHOT project in the reactor projects list." > > I don't understand why is a must to start releasing from a snapshot > version? > > Regards, > Tibor > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Block level elements do not appear in output
You use 'mvn site' to generate apt files from apt source files? I guess you mean html? In this case the title and author end up in the html , so you don't see them when you view the file with a browser. -Lukas Trevor Harmon wrote: Hi, My APT file declares block level elements such as a title and author, as defined by the APT format: http://maven.apache.org/doxia/references/apt-format.html However, when I run "mvn site", the APT file that is generated is missing the block level elements. Is this a bug? Trevor
release plugin only works with snapshot projects.
Hi. If I try to prepare a multi-project whose version is a non-snapshot version, it throws an exception: "You don't have a SNAPSHOT project in the reactor projects list." I don't understand why is a must to start releasing from a snapshot version? Regards, Tibor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Older Versions of m2eclipse
Hi, I cannot see the source of workspace projects in eclipse due bug http://jira.codehaus.org/browse/MNGECLIPSE-983 . It will get fixed in 0.9.8 but I need a workaround till then. Is it possible to install historic versions (I guess the problem stepped in 0.9.6) of m2eclipse? Where can I find older builds? Or do I have to build them on my own? Regards. Christian Kalkhoff - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot compile simple code
The missing symbol method was added in Java 1.5. Maven defaults to source
level 1.4. Set your source/target to a minimum of 1.5 on the
maven-compiler-plugin, see
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html.
Brett
On Mon, Jan 12, 2009 at 10:11 PM, SamadLotia wrote:
>
> Hello fellow Maven users,
> I have been trying to compile an OSGi project created using the PAX
> scripts.
> In the source file ConsoleTaskManager.java on line 15 I have written:
>
> System.out.println(java.lang.String.format("%s", "Why will not this
> compile?"));
>
> When I type "mvn install", I get the following error message:
>
> [INFO] [pax:compile]
> [INFO] Compiling 5 source files to
> /Users/slotia/src/csplugins-slotia/work-pir-api/target/classes
> [INFO] [recovering meta-data]
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
>
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
>
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
> If I uncomment the offending line, the project compiles fine. I also wrote
> a
> 5-line class file with the offending line, and it compiles fine with javac.
> This suggests that there probably isn't a problem with the JDK. I have
> tried
> to clean the project, which deletes the target directory, delete the runner
> directory, and delete the .m2 directory, but it still does not compile.
>
> Here are some specs of my system:
> OS: Mac OS X 10.5.6
> Java: 1.5.0_16-b06-284 32-bit
> Maven: 2.0.9
>
> I am completely lost as to how to fix this. Any help would be greatly
> appreciated. Thank you.
> --
> View this message in context:
> http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412538.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: Maven Parameters
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Add list of the objects to your mojo /** * List of Orders * * @parameter */ private List orders = new ArrayList(); and in your pom.xml (within the config section of your mojo), specify the following: 123 8 ... See 'Parameter Types With Multiple Values' at [1] for more info. Cheers, Johan [1] http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Saket Lakshminarayan Chiluveru wrote: > Hi, > > How can I pass a set of objects as parameters into a Mojo. > > e.g an Xml of the following format > > > 123 > 8 > > > > 123453 > 2 > > > > I need to pass this into a collection of objects. How do I do this ? > > > > > Saket L.C > Technical Architect | CME | TELENET | Extn 74150 > > Do or Do Not, there is no try -- yoda (star wars) > > > 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*** > - -- you too? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJaykQpHYnED7evioRAv4IAJ9y7y1usI72TkmFrVaAB0bh4XOM2QCdE11p H7sQJsQ+uqHRRcXdxb9l/58= =g0yu -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot compile simple code
What does the following command output: mvn -version especially the Java version -- View this message in context: http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412753.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: Cannot compile simple code
I apologize for the following typo: "If I uncomment the offending line",
which I meant to say, "If I comment the offending line".
SamadLotia wrote:
>
> Hello fellow Maven users,
> I have been trying to compile an OSGi project created using the PAX
> scripts. In the source file ConsoleTaskManager.java on line 15 I have
> written:
>
> System.out.println(java.lang.String.format("%s", "Why will not this
> compile?"));
>
> When I type "mvn install", I get the following error message:
>
> [INFO] [pax:compile]
> [INFO] Compiling 5 source files to
> /Users/slotia/src/csplugins-slotia/work-pir-api/target/classes
> [INFO] [recovering meta-data]
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
> If I uncomment the offending line, the project compiles fine. I also wrote
> a 5-line class file with the offending line, and it compiles fine with
> javac. This suggests that there probably isn't a problem with the JDK. I
> have tried to clean the project, which deletes the target directory,
> delete the runner directory, and delete the .m2 directory, but it still
> does not compile.
>
> Here are some specs of my system:
> OS: Mac OS X 10.5.6
> Java: 1.5.0_16-b06-284 32-bit
> Maven: 2.0.9
>
> I am completely lost as to how to fix this. Any help would be greatly
> appreciated. Thank you.
>
--
View this message in context:
http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412571.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
Cannot compile simple code
Hello fellow Maven users,
I have been trying to compile an OSGi project created using the PAX scripts.
In the source file ConsoleTaskManager.java on line 15 I have written:
System.out.println(java.lang.String.format("%s", "Why will not this
compile?"));
When I type "mvn install", I get the following error message:
[INFO] [pax:compile]
[INFO] Compiling 5 source files to
/Users/slotia/src/csplugins-slotia/work-pir-api/target/classes
[INFO] [recovering meta-data]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
cannot find symbol
symbol : method format(java.lang.String,java.lang.String)
location: class java.lang.String
/Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
cannot find symbol
symbol : method format(java.lang.String,java.lang.String)
location: class java.lang.String
If I uncomment the offending line, the project compiles fine. I also wrote a
5-line class file with the offending line, and it compiles fine with javac.
This suggests that there probably isn't a problem with the JDK. I have tried
to clean the project, which deletes the target directory, delete the runner
directory, and delete the .m2 directory, but it still does not compile.
Here are some specs of my system:
OS: Mac OS X 10.5.6
Java: 1.5.0_16-b06-284 32-bit
Maven: 2.0.9
I am completely lost as to how to fix this. Any help would be greatly
appreciated. Thank you.
--
View this message in context:
http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412538.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
Maven Parameters
Hi, How can I pass a set of objects as parameters into a Mojo. e.g an Xml of the following format 123 8 123453 2 I need to pass this into a collection of objects. How do I do this ? Saket L.C Technical Architect | CME | TELENET | Extn 74150 Do or Do Not, there is no try -- yoda (star wars) 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***
Re: Mvn eclipse:eclipse - strange M2_REPO settings
I am experiencing this too, and I found a jira for this issue which was closed but I think should be reopened. http://jira.codehaus.org/browse/MECLIPSE-408 Regards, Neil Crow. Ian Orford wrote: > > Maven 2.0.9 > maven-eclipse-plugin 2.5.1 > Eclipse 3.4.1 > > Some time ago, my "mvn eclipse:eclipse" commands started misbehaving. I > had been using it for ages previously. > > My repo on my development workstation is in C:\Dev\.m2\repository. > > The .classpath files that are generated when I run "mvn eclipse:eclipse" > on a project include the whole path. For example, one of the entries is: > > > path="M2_REPO/dev/.m2/repository/org/springframework/spring/2.5.1/spring > -2.5.1.jar" > > sourcepath="M2_REPO/dev/.m2/repository/org/springframework/spring/2.5.1/ > spring-2.5.1-sources.jar"/> > > So for this to work, I have to set my M2_REPO variable to just "C:/" and > not the path to the repo. > I'm not sure what I upgraded that caused this behaviour. > > Anyone have any clues? > > Many thanks, > Ian > -- View this message in context: http://www.nabble.com/Mvn-eclipse%3Aeclipse---strange-M2_REPO-settings-tp20541566p21412358.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
unable to set repo loc using maven release plugin 2.0-beta-8
Hi Release Plugin Gurus, I want to specify a local maven repo. Using maven release plugin 2.0-beta-8, I tried the combinations of "-Darguments=-Dmaven.repo.local=...", "-Darguments=-Dmaven.home...", -DlocalRepoDirectory=..." and/or "-DmavenHome=...", it always return /.m2/repository not found. Is this a known issue? Is there a workaround? This was working in 2.0-beta-7. However, in the 2.0-beta-7 release, the parameters releaseVersion and developmentVersion are not working. See: http://jira.codehaus.org/browse/MRELEASE-389 Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: required artifact is missing ......
To add to what Wendy posted; the screenshot shows that the artifact is under D:\Daten\maven2-local\. Is that your Maven repository? Have you configured Maven to use this as the repository (through settings.xml)? By default Maven uses the user's home directory as the repository. thomas2004 wrote: > > Here is the screen-shot of my repository. Can you see what is wrong? > > http://www.nabble.com/file/p21373356/pom.jpg > > > -- View this message in context: http://www.nabble.com/required-artifact-is-missing-..-tp21372605p21410613.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
