Here is my final update,
I could not bind to the package phase as described in the documentation.
http://maven.apache.org/plugins/maven-dependency-plugin/usage.html (I copied
the template, set the variables as needed and issued 'mvn package' but the
copy was not triggered)
Maybe someone could shed
I guess the repository is not an issue. I can't deploy the jars/wars/ears
with artifact-x.z.y-snapshot name formatting.
Since I will not use Maven's deployment mechanism I think I will resort to
the dependency plugin. It will in a sense mimic what happens now. Artifacts
are ftp-ed from M1 reposito
On Tue, Jun 22, 2010 at 12:00 PM, D D wrote:
> I'm converting projects from M1 to M2. Due to restrictions imposed from
> "above" - I'm not allowed to change anything - including names of artifacts.
> In M1 implementation the artifacts did not contain versions in their names.
>
> At this point I ha
I've not tried it, but I think Nexus has support for creating a M1
"virtual" repository that will "convert" a M2 to look like a M1
repository.
http://www.sonatype.com/books/nexus-book/reference/config-sect-manage-repo.html
On Tue, Jun 22, 2010 at 10:00 AM, D D wrote:
> I'm converting projects fr
I'm converting projects from M1 to M2. Due to restrictions imposed from
"above" - I'm not allowed to change anything - including names of artifacts.
In M1 implementation the artifacts did not contain versions in their names.
At this point I have over 100 artifacts that will be ftp-ed to an
applica
Yes, but it is only a Flex project not a Flex<->BlazeDS<->J2EE project.
I already have my Flex/BlazeDS/J2EE project set up with Eclipse.
But I need to do it "maven-driven".
Best Regards Phantomias.
Am 12.06.2010 um 16:46 schrieb Martin Gainty:
there is an existing flex-template you can use u
On Tue, Jun 22, 2010 at 10:54 AM, D D wrote:
> Is there an easy way to deploy an artifact such it doesn't include version
> in its name?
> For example: when moduleA is deployed through 'mvn deploy' I
> get moduleA-X.Y-SNAPSHOT.jar but what I need is moduleA.jar.
The Maven repo has a fixed structu
That will not affect the artifact's file name in the repo, just in the
target folder.
/Anders
Den 22 jun 2010 16.58, "Shan Syed" skrev:
do you need the artifact's file name to retain the groupId/version info? if
not, specify moduleA in the section of your
POM
On Tue, Jun 22, 2010 at 10:54 AM
do you need the artifact's file name to retain the groupId/version info? if
not, specify moduleA in the section of your
POM
On Tue, Jun 22, 2010 at 10:54 AM, D D wrote:
> Hello,
>
> Is there an easy way to deploy an artifact such it doesn't include version
> in its name?
>
> For example: when m
Hello,
Is there an easy way to deploy an artifact such it doesn't include version
in its name?
For example: when moduleA is deployed through 'mvn deploy' I
get moduleA-X.Y-SNAPSHOT.jar but what I need is moduleA.jar.
Thanks,
Dave
> Which version of module3 is used and give maven a error or at least a
> warning?
If you lock down versions using [1.2.3] tags then
you can cause mismatches in versions to throw errors during the Maven
build.
Also you could use enforcer plugin to guarantee certain versions of
dependencies and pl
The version "closest" to your project wins. In your case that would be
module3.v1.
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
This is managed by Maven and you don't get any warnings.
However, you can always use some mojo like dependency:resolve to view th
Hello,
in which way resolve maven inherited dependencys.
E.G. module1.v1 -> depends module2.v1 and module3.v1
module2.v1 -> depends module3.v2
Which version of module3 is used and give maven a error or at least a
warning?
Yours Rüdiger
--
View this message in context:
http://maven-user
Having different "flavors" of your artifacts, depending on which environment
you build for is not recommended. In Maven, a specific artifact defined by
GAV (i.e. a specific version of your artifact) cannot (should not) change.
We've had numerous discussions regarding this on the list. It simply isn
You can disable the use of the release profile. See the link Nick sent.
/Anders
On Tue, Jun 22, 2010 at 11:53, Daniele Dellafiore wrote:
> Ok, the problem here is that if this conflict with existent source and
> javadocs generation configuration, it causes the release to fail.
>
> On Tue, Jun 2
Ok, the problem here is that if this conflict with existent source and
javadocs generation configuration, it causes the release to fail.
On Tue, Jun 22, 2010 at 11:50 AM, Nick Stolwijk wrote:
> M-R-P activates a release profile by default, which contains the
> source and javadocs. See [1]
>
> [1]
M-R-P activates a release profile by default, which contains the
source and javadocs. See [1]
[1]
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.ipro
ok, I changed executions goal from jar-no-fork to just "jar" and it works
I think that m-r-p by default has the attach-sources on the goal jar active
and if I add a jar-no-fork executions, they are summed.
In fact nowhere in my config I tell maven to make javadoc but the release
plugin just make it
I fixed the last problem removing myProject inheritance from the company
pom.
Now I am stucked cause the release plugin is deploying the source artifact
two times and the second time Nexus give me a 400 cause it does not allow to
overwrite an artifact in the release repository, and it's right.
It
Hi all,
I want to create an assembly with the assembly plugin, but exclude files -
which I fail.
I use:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/maven-ass
Maven failed to resolve repo1.maven.org. I tried manually it resolves.
To further dig into
the matter I tried to hit the URL manually using Firefox:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-4/maven-archetype-plugin-2.0-alpha-4.pom
It worked, then I tri
Sorry, it should read "wget does NOT work".
/Anders
On Tue, Jun 22, 2010 at 09:09, Anders Hammar wrote:
> Yes, wget does work against central. It is blocked (by central).
>
> /Anders
>
>
> On Tue, Jun 22, 2010 at 08:00, Akshay Dev Wankhede <
> akshay.sys...@gmail.com> wrote:
>
>> Maven failed t
Yes, wget does work against central. It is blocked (by central).
/Anders
On Tue, Jun 22, 2010 at 08:00, Akshay Dev Wankhede
wrote:
> Maven failed to resolve repo1.maven.org. I tried manually it resolves.
> To further dig into
> the matter I tried to hit the URL manually using Firefox:
>
> http:/
I haven't been able to figure out how to set the primary artifact file for an
Ant based plugin similar to the way it can be set in a Java based a plugin.
A simple example of what I'd like to be able to do is provided by the zip
plugin in the sandbox (See line 162 of
http://svn.apache.org/viewvc/
Hello Benyi,
What's so wrong with having module-A installed in your local repository?
Regards,
Stevo.
On Tue, Jun 22, 2010 at 12:29 AM, Benyi Wang wrote:
> I have a maven project like this:
>
> my-project
> module-A
> module-B
>
> two modules A and B are in the sibling folders with the parent
25 matches
Mail list logo
