nope.
On Mon, Apr 12, 2010 at 4:43 AM, Henika Tekwani wrote:
> Hi,
>
> As we know that when we deploy an artifact to a snapshot repository the
> SNAPHOT keyword in the artifact version, say 9.5.0-SNAPSHOT, is replaced by a
> timestamp number (e.g., my-app-9.5.0-20100412.084615-1.jar). In this c
Hi All,
I tried it on just Windows. Later I will try on Linux. I am sorry that I
have not explained clearly.
On Tue, Apr 13, 2010 at 9:29 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 13 April 2010 13:33, Eric Chatellier wrote:
>
> > Le 13/04/2010 14:29, Garin Yan a écrit
On 4/13/2010 10:15 AM, Marshall Schor wrote:
>
> On 4/13/2010 10:04 AM, Marshall Schor wrote:
>
>> In the org.apache:apache:7 pom, a common parent-pom for apache projects,
>> I see in the apache-release profile section, a part which creates the
>> source-release artifact.
>>
>> This runs the m
Hello,
I have a question for advanced users: I want to add to an existing custom
packaging a goal of my POJO for the deploy phase.
Normally, a packaging is defined through a Plexus components.xml file where
you have to specify for all phases the inpacted mojos and goals to run.
So if I add a parti
I have a project that builds a war file using Maven 2.2. I would like to serve
jnlp file that can be used to start an application remotely using Java Web
Start. I need to do following things:
1. Sign the project jar file as well as all dependent jar files
2. Copy jar files in lib directory
That worked, thanks Tim!
Tim O'Brien wrote:
Frank,
In Project C's pom.xml, use the "single" goal instead of the
"assembly" goal. This should fix the problem.
Tim
On Tue, Apr 13, 2010 at 12:01 PM, Frank Maritato
wrote:
Hi All,
I have a multi module project and my "mvn package" command fro
Frank,
In Project C's pom.xml, use the "single" goal instead of the
"assembly" goal. This should fix the problem.
Tim
On Tue, Apr 13, 2010 at 12:01 PM, Frank Maritato
wrote:
> Hi All,
>
> I have a multi module project and my "mvn package" command from the top
> level is failing when one of my
I was going to say Hitch Hikers Guide to Galaxy ;-).
> -Original Message-
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Sent: Monday, April 12, 2010 2:01 PM
> To: users@maven.apache.org
> Subject: RE: some question
>
>
> appears someone on this list has been watching Dr Who
>
>
ok, thanks so much.
noemi.
--
View this message in context:
http://old.nabble.com/package-org.springframework.osgi.service.importer-does-not-exist-tp27143992p28233196.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
> I hope you can understand me: I had to change my pom ( that worked fine
> until friday) only just because suddenly eclipse showed me an error on the
> pom.
Then Eclipse is/was wrong. Your pom was correct before.
Wayne
-
To uns
Hi,
I try to explain what happen better:
I had no problems for months,
my pom looked like this:
.
but suddenly, without any change in it, I had an error: eclipse told me that
my pom was wrong,... so I changed it to:(only to fix
Hi All,
I have a multi module project and my "mvn package" command from the top
level is failing when one of my modules defines the assembly plugin with
an block to make it part of the package phase. Specifically
you will see that moduleC cannot resolve the artifact in moduleA and it
looks l
On Tue, Apr 13, 2010 at 12:19 PM, Viv Kapadekar wrote:
> The core module depends on shared-module.jar. But since both are under
> development we have to run mvn install on shared-module before running any
> commands on core-module. Is it possible that compilation of core, first
> triggers mvn in
> development we have to run mvn install on shared-module before running any
> commands on core-module. Is it possible that compilation of core, first
> triggers mvn install of shared-module? I know if I do it from parent, it
> will work fine. But usually we work on individual modules, so being ab
> this moment it compiles and runs ok, so, I added a tag
> just before (I've tried this before,
So you had:
project
-dependencies [...]
And you changed it to:
project
-dependencyManagement
--dependencies [...]
This has the effect of removing the dependencies from your project. As
a result, the
Hi
I have this structure
{ parent}
{core-module}
pom.xml
{shared-module}
pom.xml
pom.xml
The core module depends on shared-module.jar. But since both
Hi,
Does anybody know if there's existing mojo to allow individual modules in a
multi-module project to point to different SCM urls? So instead of having
the entire project living in a single subversion tree it you could use
something like scm:bootstrap to check out dependent modules from various
Hi Alcaan, i got the same exactly problem last weekend.
On friday evening the pom show me an error, I don't know why because until
this moment it compiles and runs ok, so, I added a tag
just before (I've tried this before,
but it hasn't run this way) so, te error in the pom dissapear, but it
doe
On Tue, Apr 13, 2010 at 10:30 AM, Wayne Fay wrote:
>> I use Maven 2 in a project and i would like to link plugin execution to the
>> execution of another plugin.
>
> No, you cannot link plugin executions.
>
>> With that, I thought that execution of my id process-ant was like a phase
>> process-ant
> I use Maven 2 in a project and i would like to link plugin execution to the
> execution of another plugin.
No, you cannot link plugin executions.
> With that, I thought that execution of my id process-ant was like a phase
> process-ant that I could bind to executions of others plugins.
No, it
You have to reference an existing phase. The "process-ant' phase does
not exist in the Default Maven Lifecycle. Look at the Lifecycle
Reference on this page:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics
On Mon, Apr 12, 2010 at 5:22 PM
You can do whatever you need to do with versions, but this isn't
really the workflow associated with the maven-release-plugin. The
release plugin exists to automate the following process:
Prepare
1. Take the current working copy - assume you have version 1.2-SNAPSHOT
2. Update the version numb
On 4/13/2010 10:04 AM, Marshall Schor wrote:
> In the org.apache:apache:7 pom, a common parent-pom for apache projects,
> I see in the apache-release profile section, a part which creates the
> source-release artifact.
>
> This runs the maven-assembly-plugin, and passes it a dependency on
> org.a
In the org.apache:apache:7 pom, a common parent-pom for apache projects,
I see in the apache-release profile section, a part which creates the
source-release artifact.
This runs the maven-assembly-plugin, and passes it a dependency on
org.apache.apache.resources:apache-source-release-assembly-desc
On 13 April 2010 13:33, Eric Chatellier wrote:
> Le 13/04/2010 14:29, Garin Yan a écrit :
> > Hi Amaresh,
> >
> > The name of the POM is case-insensitive. So you can name the POM file as
> > pom.xml, POM.XML or pOm.xMl.
> >
> Maybe on Windows, but it's not working on unix systems.
>
> $ mv pom.xm
Do you have a reference for this? It is not true AFAIK.
On Tue, Apr 13, 2010 at 8:29 AM, Garin Yan wrote:
> Hi Amaresh,
>
> The name of the POM is case-insensitive. So you can name the POM file as
> pom.xml, POM.XML or pOm.xMl.
>
> On Tue, Apr 13, 2010 at 8:09 PM, amaresh mourya >wrote:
>
> >
That's because Windows is case-insensitive.
On Tue, Apr 13, 2010 at 8:42 AM, amaresh mourya wrote:
> This is working fine on windows..means POM.XML seems to be valid name.
> I had one pom.xml , renamed it to POM.XML and mvn install worked
> successfully.
>
>
> On Tue, Apr 13, 2010 at 6:03 PM, Eri
This is working fine on windows..means POM.XML seems to be valid name.
I had one pom.xml , renamed it to POM.XML and mvn install worked
successfully.
On Tue, Apr 13, 2010 at 6:03 PM, Eric Chatellier
wrote:
> Le 13/04/2010 14:29, Garin Yan a écrit :
> > Hi Amaresh,
> >
> > The name of the POM is
Le 13/04/2010 14:29, Garin Yan a écrit :
> Hi Amaresh,
>
> The name of the POM is case-insensitive. So you can name the POM file as
> pom.xml, POM.XML or pOm.xMl.
>
Maybe on Windows, but it's not working on unix systems.
$ mv pom.xml POM.xml
$ mvn clean install
[INFO] Scanning for projects...
[
Thanks
On Tue, Apr 13, 2010 at 5:59 PM, Garin Yan wrote:
> Hi Amaresh,
>
> The name of the POM is case-insensitive. So you can name the POM file as
> pom.xml, POM.XML or pOm.xMl.
>
> On Tue, Apr 13, 2010 at 8:09 PM, amaresh mourya >wrote:
>
> > Hi All,
> >
> > I am in need of having check on a
Hi Amaresh,
The name of the POM is case-insensitive. So you can name the POM file as
pom.xml, POM.XML or pOm.xMl.
On Tue, Apr 13, 2010 at 8:09 PM, amaresh mourya wrote:
> Hi All,
>
> I am in need of having check on a set of xml documents in search of
> potential POMs. So is it necessary that nam
Hi All,
I am in need of having check on a set of xml documents in search of
potential POMs. So is it necessary that name of the xml file should be
pom.xml and it cannot be POM.XML?
Thanks,
Amaresh
Hi Eydal,
as far as I know you need to set the environment variable 'LD_LIBRARY_PATH'
before you start the java application.
export LD_LIBRARY_PATH=/path/with/the/so/file
after that, starting the java app.
CU,
Jochen
2010/4/12 eyal edri
> Hi,
>
> i'm deploying a java application (jar) on a l
Hi again,
I've now created a test case, at
http://github.com/rickyclarkson/maven-git-testcase
It's started to affect more projects, as I'm moving over to git a
project at a time, and I'm resorting to manual releases at the moment.
I've already made a mistake, though not a serious one, so I'm kee
Hello,
I'd like to perform a release (with mavean-release-plugin) with this
process :
Make release candidate v1-beta1 => ok
Perform tests
If tests are ko, make a new relesase candidate v1-beta2 => ok
Perform tests
If tests are ok, i'd like to make the final release (v1) and i want to be
sure th
Hi,
I've got a little problem concerning an exploded war. I'm using the
maven-war-plugin to assemble it.
The project to which I've been attached to needs the pom.properties file to
run. When I'm assembling the frontend as a zipped war with war:war, everything
is working fine. But when I'm asse
dependency:unpack or dependency:unpack-dependencies with the target
directory being ${project.build.testOutputDirectory}
On 12 April 2010 21:57, Madhanraj Meignanam wrote:
> Hi All,
>
> Is there any plug-in that helps to invoke the JUnit tests of a jar. We are
> having a requirement to run tests
37 matches
Mail list logo
