AFAIK a dot component in a path is still a valid URL so IMO the bug is
on the server side. While it is probably a good idea for maven to
normalize the path before the PUT, that's no reason to throw a 500
(internal server error...)
Cheers,
-Lukas
Dennis Lundberg wrote:
Hi
After looking
@Denis: I will create issues for both plugins (site and wagon) as you suggested.
@Olivier: Sorry, by SCM is totally inefficient for site deployment.
The best method for site deployment would be SCP but googlecode
doesn't support it.
@Lukas: You are right, the URL with '/./' is still a valid URL.
I'm having an issue with marking my repository as
updatePolicynever/updatePolicy. It seems as though even with the never
parameter, the first time an artifact is referenced, an initial check to the
remote repo happens. After that, the metadata.xml is created locally and
further checks for
Hi
With site 2.0 plugin it was possible to add reporting plugin in a profile
without redefining all other reporting plugins declared in the main
reporting section. One example of the usecase for this would be when some
heavy tests with maven invoker plugin were configured only in the profile
For further information please track the following issues:
http://jira.codehaus.org/browse/MSITE-531
http://jira.codehaus.org/browse/MOJO-1611
On 16 December 2010 09:29, Marcin Kuthan marcin.kut...@gmail.com wrote:
@Denis: I will create issues for both plugins (site and wagon) as you
Yes you are right. Maven should never check the remote repo if you have
configured the updatePolicy to never and the artefact is locally installed.
From the documentation
updatePolicy String The frequency for downloading updates - can be
always, daily (default), interval:XXX (in minutes) or
On 16/12/2010, at 6:19 PM, Martin Höller wrote:
Hi Ron!
Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler:
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test machines and production less painful.
I saw you mentioning this a few
Problem seems to be fixed when using aggregate-jar goal (instead of
aggregate) for version 2.7 of the plugin.
--
View this message in context:
http://maven-users.828.n2.nabble.com/maven-javadoc-plugin-aggregate-and-maven-plugin-module-does-not-work-tp4974133p5841408.html
Sent from the maven
Hi,
I have downloaded apache-maven-3.0.1 and noe not able to add this to Eclipse
3.5, I extracted the zip file and copy pasted the folder in plugin folder of
Eclipse.
Can you please help me to resolve the problem.
Regards,
Neeta Rathi
CAUTION - Disclaimer *
This
Maven 3.0.1 is not an eclipse-plugin. It is a command line tool.
You want m2eclipse for Maven integration in Eclipse. It's moving to Eclipse,
but the latest version is still available according to the info at
http://m2eclipse.sonatype.org. There's also a separate mailing list for it.
/Anders
On
Hi,
since quite a while I am using Maven and Eclipse together with the
Eclipse plugin for Maven and the Maven plugin for Eclipse. And it is
just great.
But in the version 2.8 of the Eclipse plugin for Maven I am (hardly)
missing the goal m2eclipse.
How can I tell the version 2.8 of the
You can't (in 2.8) - you can specify the old version of the plugin with the
m2eclipse goal on the command line.
Or (preffered)
just import the projects in eclipse as maven projects, and let m2eclipse create
your project files with the correct natures.
/James
-Original Message-
From:
I tested with a very simple test case and made sure to delete the dependency
and dependent from the local reposoitory.
With maven 2.2.1 it behaves as I posted, always doing one initial check and
pulling down the newer version if available.
With maven 3.0.1 it behaves correctly and does not
Kind of a newb9ie question:
I wish to update a project to use the later version of a dependency.
There are some incompatibilities and I'd like to try to come up to speed
quickly. In the past I've simply gone to the project's web site and
browsed or downloaded javadoc and/or source. But
On Thu, Dec 16, 2010 at 8:46 AM, Steve Cohen sco...@javactivity.org wrote:
I wish to update a project to use the later version of a dependency. There
are some incompatibilities and I'd like to try to come up to speed quickly.
In the past I've simply gone to the project's web site and browsed
Hello
I'm using maven 3.0.1
I got following ouput everytime I've built a child project. The missing
dependencies are declared in the parent project. The curious thing is
that the build never fails and the [WARNING] messages are displayed at
the end of the build. Futhermore are all of those
On Thu, Dec 16, 2010 at 8:58 AM, Moser, Christian c...@metrohm.com wrote:
Hello
I'm using maven 3.0.1
I got following ouput everytime I've built a child project. The missing
dependencies are declared in the parent project. The curious thing is
that the build never fails and the [WARNING]
Kind of a newb9ie question:
I wish to update a project to use the later version of a dependency.
There are some incompatibilities and I'd like to try to come up to speed
quickly. In the past I've simply gone to the project's web site and
browsed or downloaded javadoc and/or source. But
On 16/12/2010 2:19 AM, Martin Höller wrote:
Hi Ron!
Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler:
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test machines and production less painful.
I saw you mentioning this a few times now.
On 16/12/2010 4:23 AM, Brett Porter wrote:
On 16/12/2010, at 6:19 PM, Martin Höller wrote:
Hi Ron!
Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler:
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test machines and production less
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
to project C but Maven still complains:
Failed to execute goal on project C: Could not resolve dependencies for
project com.foo:C:jar:1.0-SNAPSHOT: Failure to
Hi list,
A few weeks ago I think I've installed this feature from:
m2eclipse Extras - http://m2eclipse.sonatype.org/sites/m2e-extras
But now the feature is not available any more ?!?!
Any Idea ??
Thanks Fredy
-
To unsubscribe,
Thanks for your response!
The pom's are also located in my local repo. What I found in Artifactory is
that the maven-metadata.xml does exist on the int_icons directory which
contains one deployed version of this library/artifact. The folder 2.6.0
contains jar, sources, pom, javadoc but
Please use the M2Eclipse list for these questions. This has already been
answered on the M2E lists.
On Dec 16, 2010, at 9:58 AM, Hauschel Fred Robert wrote:
Hi list,
A few weeks ago I think I've installed this feature from:
m2eclipse Extras - http://m2eclipse.sonatype.org/sites/m2e-extras
cowwoc wrote:
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
-
To unsubscribe, e-mail:
I've fixed the problem with the missing checksums in artifactory, I was able to
generate them with admin rights.
The problem with the missing pom still remains, it seems this is a maven 3.0.1
bug..
-Ursprüngliche Nachricht-
Von: Moser, Christian [mailto:c...@metrohm.com]
Gesendet:
Jörg Schaible-3 wrote:
cowwoc wrote:
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
Jörg,
Isn't one of the main selling points of Maven the ability to
On 12/16/2010 07:52 AM, Wendy Smoak wrote:
On Thu, Dec 16, 2010 at 8:46 AM, Steve Cohensco...@javactivity.org wrote:
I wish to update a project to use the later version of a dependency. There
are some incompatibilities and I'd like to try to come up to speed quickly.
In the past I've simply
If one is using a custom mojo to compute few things and save the result as a
string. Is it possible to expose that string as a property to the pom (except
using System.setProperty)?
Is there a property corresponding to the default resource location
${basedir}/src/main/resources?
Thanks
Ankush
Hi Gili,
cowwoc wrote:
Jörg Schaible-3 wrote:
cowwoc wrote:
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
Jörg,
Isn't one of the main selling
On 16/12/2010 11:13 AM, Steve Cohen wrote:
On 12/16/2010 07:52 AM, Wendy Smoak wrote:
On Thu, Dec 16, 2010 at 8:46 AM, Steve Cohensco...@javactivity.org
wrote:
I wish to update a project to use the later version of a dependency.
There
are some incompatibilities and I'd like to try to come up
I'm just learning Maven and trying this demo:
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html.
I built the files as described. The install step works. The run step
gets this error: Could not find goal 'hello' in plugin
org.myproject.plugins:hello-plugin:2.0 among available
[INFO] Installing
C:\tmp\maven-user\maven-script-ant\target\hello-plugin-1.0-SNAPSHOT.jar
to C:\Documents and Settings\oldmad\.m2\repository\org\mypro
ject\plugins\hello-plugin\1.0-SNAPSHOT\hello-plugin-1.0-SNAPSHOT.jar
[ERROR] Could not find goal 'hello' in plugin
That appears to be an artifact of some other experiments that I did. I deleted
the contents of my .m2\repository\org\myproject\plugins file and ran again. It
gets this error:
C:\tmp\maven-user\maven-script-antmvn org.myproject.plugins:hello-plugin:hello
[INFO] Scanning for projects...
Hello,
I'm trying to make a set of archetypes 2.0 with templates using
velocity, but can't find any reference. I've tried reversing a project
to archetype, but then I don't get the archetype.xml file
What I need are some guides to start, like the namespace for the
archetype.xml 2.0 and how to
Sorry about the confusion. By the way, does the phrase “This plugin
has 0 goal:” give a hint to the problem? Perhaps I don’t understand
the difference between goal prefixes and goals.
I've built Java and Groovy plugins for Maven before but never an Ant
plugin. So its possible that I simply
Hi all,
I am experiencing a kind of chicken-and-egg problem in my usage of the
m-pmd-p, the m-checkstyle-p, and the m-license-p. All these plugins are
capable of loading their respective configurations (rulesets or license
headers) from the plugin's classpath. As such it seems sensible to
create
Hi Steve,
Note sure what you are trying to do here but source and javadoc dependencies
are not defined to be added as dependencies. Instead they are used by tools
like m2eclipse [1] that download them whenever you access a class of one of
your dependency. M2eclipse is really convenient, you
Hi
Those docs are not up-to-date.
I have a small Maven plugin written in Ant that works. I'll try to
update the docs shortly using that as an example.
On 2010-12-16 18:28, dan.old...@emc.com wrote:
I'm just learning Maven and trying this demo:
Hi all,
I know maven install command is to upload your artifact to local repository.
However, I have a question on the version of the artifact.
By default, the version is defined in
projectversion/version/project.
Is it possible to override this in profiles?
What I tried
profile
idrelease/id
I just upgraded to Maven3 from Maven2 today, and when I run mvn.bat
-version, this is what I see:
Apache Maven 2.2.1 (r801777; 2009-08-06 13:16:01-0600)
Java version: 1.6.0_23
Java home: C:\Java\jdk6
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp
I have default properties listed in my pom like this:
properties
liquibaseTestingEnabledfalse/liquibaseTestingEnabled
testHibernateHbm2DdlAutocreate/testHibernateHbm2DdlAuto
testEclipseLinkDdlGenerationdrop-and-create-tables/testEclipseLinkDdlGeneration
You can't.
/Anders (mobile)
Den 16 dec 2010 21.42 skrev Maven Yu mavendavi...@gmail.com:
Hi all,
I know maven install command is to upload your artifact to local
repository.
However, I have a question on the version of the artifact.
By default, the version is defined in
Thanks for the reply.
Had been trying to avoid that but seems I cannot. Especially since
moving to the next SNAPSHOT version gets you to:
mvn update-versioin-to-release-plugin mvn clean install mvn
update-version-to-next-snapshot-plugin
On Wed, Dec 15, 2010 at 7:36 PM, Justin Edelson
On 2010-12-16 22:15, Andre M wrote:
I just upgraded to Maven3 from Maven2 today, and when I run mvn.bat
-version, this is what I see:
Try .\mvn.bat just to be sure that it is not an issue with your path.
Apache Maven 2.2.1 (r801777; 2009-08-06 13:16:01-0600)
Java version:
After reading about the pitfalls and spotty implementation of
pseudo-inheritance of profiles, I can report that it appears that for a
profile defined in a parent pom you can activate it from a child as long as
the child doesn't try to activate it using a property value.
So a profile defined in a
Actually, that's what I am using. Ok, where in the m2eclipse user
interface SHOULD I add the javadoc dependencies? Is it in the
dependencies section of the POM editor and if not, then where?
On 12/16/2010 02:36 PM, Reynald Borer wrote:
Hi Steve,
Note sure what you are trying to do here
What's the best way to resolve this kind of chicken-and-egg problem
without introducing too many extra projects just to break the cycle? Any
This is exactly what you have to do. The rulesets should be packaged
and versioned independent of the project. Ideally you'd have one
corporate ruleset
I just upgraded to Maven3 from Maven2 today, and when I run mvn.bat
-version, this is what I see:
If you were on a Unix platform, I'd tell you to run which mvn to be
sure that you're running the binary/batch file you believe you're
executing... but you're on Windows.
Perhaps use Sysinternals
Hi sim085,
I know the EAR you made can be deployed on JBoss successfully. Maybe,
you could try to add the Class-Path key in MANIFEST.MF of EJB JAR. If it
doesn't work yet, please refer mechanism of class loaders of Geronimo.
Hope it is helpful to you.
Thanks,
Diego
-Original
You don't specify anything, you just either configure m2e to download
sources/javadoc och right-click on the dependency and select
Maven-Download
http://www.sonatype.com/books/m2eclipse-book/reference/dependencies.html#dependencies-sect-downloading-source
/Anders
On Fri, Dec 17, 2010 at
I think the best thing is to create a test project that re-produces this.
Then create a jira and attach the test project. Explain the exact command
you execute, the actual outcome and what you expected the outcome to be.
Then it will be easy for someone to spot if it's a Maven issue or incorrect
Hi!
Am Donnerstag 16 Dezember 2010, 15:07:19 schrieb Ron Wheeler:
On 16/12/2010 2:19 AM, Martin Höller wrote:
Hi Ron!
Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler:
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test
I am trying to create my first Maven project with Maven 3.0.1. First I got
problem in downloading the plugins then I downloaded the jar files manually
and put those in the local repository. Now it is not showing error for the
plugin jars but for maven-metadata.xml. I downloaded the xmls files as
I am trying to create my first Maven project with Maven 3.0.1. First I got
problem in downloading the plugins then I downloaded the jar files manually
and put those in the local repository. Now it is not showing error for the
plugin jars but for maven-metadata.xml. I downloaded the xmls files as
If Maven can't download the plugins something is wrong with your setup. You
need to fix that before proceeding!
Are you behind a proxy? Then you need to configure Maven to use that. Do you
have an internal repo manager? Then you need to configure Maven for that.
/Anders
On Fri, Dec 17, 2010 at
56 matches
Mail list logo
