Thanks Ramsey, but everything seems to be working fine with the snapshot
version for me, now that I’m manually copying resources like Henrique
suggested. Granted, I’m not using the release plugin.
But I’d like to suggest that we change wolifecycle and move WebObjects bundle
resources to a diffe
I’ve since found that the maven release plugin doesn’t like snapshot versions
and switched back to using the 2.2.1 release version. This gives me the red Xs
again in Eclipse, but those can be silenced with lifecycle mappings. Here’s
what my current lifecycle mappings file looks like.
The snapshot version used in my pom-files is included by default by the
archetypes found at:
http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml
Which is the archetype catalog recommended for use by:
https://wiki.wocommunity.org/display/WOL/Quick+Star
Glad you got it working…
Just one question: Is there a reason why you’re using a snapshot version of
womaven-lifecycle-plugin? That’s generally not a good idea (and could have been
part of the problem).
> On 22 Mar 2016, at 8:39 PM, Hugi Thordarson wrote:
>
> Hi Lachlan,
> Here’s what my pom
This worked perfectly, thanks Henrique!
I wonder if WebObjects resources should perhaps live in a different folder than
src/main/resources? That folder is a standard part of the maven project
structure and this made for some really unexpeted behaviour.
Cheers,
- hugi
> On 22. mar. 2016, at 1
Hi Hugi,
AFAIR, the wolifecycle-maven-plugin copies all files from src/main/resources
into the Resources folder. However, you can use the maven-resources-plugin to
copy the required files into the Maven output directory.
maven-resources-plugin
2.6
Hi Lachlan,
Here’s what my pom looks like, pretty vanilla:
https://gist.github.com/anonymous/00e2cee94b185cd846af
I’m just running mvn package for the build, should I be running different goals?
Thanks for all your help :)
- hugi
> On 21. mar. 2016, at 22:36, Lachlan Deck wrote:
>
> A coup
A couple of questions:
- What’s your pom look like?
- What commands are you running?
The relevant section is the woman-lifecycle-plugin.
Your src/main/resources is a standard path for maven; that’s not your problem.
mvn clean package should create your jar in target/.
cheers,
Lachlan
> On 22
Hi Lachlan,
Thanks, I found the pom you mentioned, but I don’t quite see which parts of it
are relevant to my question?
- hugi
> On 21. mar. 2016, at 20:55, Lachlan Deck wrote:
>
> Perhaps @see the list archives for the pom I’d sent to the list in 2012.
>
> ——
> Subject: Re: Maven
> From: L
Perhaps @see the list archives for the pom I’d sent to the list in 2012.
——
Subject: Re: Maven
From: Lachlan Deck
In-Reply-To: <1fea37e9-8a7e-4c5d-836b-3c82faba6...@mac.com>
Date: Sat, 21 Jan 2012 11:01:25 +1100
Message-Id: <64800f58-ca7f-4ed4-bbc1-f69f62cfd...@gmail.com>
References: <1fea37e9-8a
OK, turns out it was Eclipse that was copying the resources to the
classes-folder… I should have known.
But the question then still remains; how do I introduce the standard maven
resources behaviour to my WO projects, i.e. make tem copy resources from
src/main/resources into my jar file.
Chee
Hi all.
I’ve begun the fun task of converting all my WO apps to maven (finally) but I’m
encountering odd behaviour with resources.
In my src/main/resources I have a couple of xml files that should end up in the
final jar (as they do with a regular java maven build). If I run “mvn pakage”
on my
12 matches
Mail list logo
