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.
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.owasp</groupId>
<artifactId>dependency-check-maven</artifactId>
<goals>
<goal>check</goal>
</goals>
<versionRange>[0.0,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>com.github.s4u.plugins</groupId>
<artifactId>pgpverify-maven-plugin</artifactId>
<goals>
<goal>check</goal>
</goals>
<versionRange>[0.0,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<goals>
<goal>unpack</goal>
<goal>copy</goal>
</goals>
<versionRange>[0.0,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.objectstyle.woproject.maven2</groupId>
<artifactId>maven-wolifecycle-plugin</artifactId>
<goals>
<goal>define-woapplication-resources</goal>
<goal>woapplication</goal>
<goal>define-woframework-resources</goal>
<goal>woframework</goal>
</goals>
<versionRange>[0.0,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
On Mar 24, 2016, at 12:00 PM, Hugi Thordarson <h...@karlmenn.is> wrote:
> 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+Start
>
> Should I be using a different version of the plugin?
>
> - hugi
>
>
>
>> On 24. mar. 2016, at 18:04, Lachlan Deck <lachlan.d...@gmail.com> wrote:
>>
>> 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 <h...@karlmenn.is> wrote:
>>>
>>> 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 <lachlan.d...@gmail.com> wrote:
>>>>
>>>> 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 Mar 2016, at 8:55 AM, Hugi Thordarson <h...@karlmenn.is> wrote:
>>>>>
>>>>> 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 <lachlan.d...@gmail.com> wrote:
>>>>>>
>>>>>> Perhaps @see the list archives for the pom I’d sent to the list in 2012.
>>>>>>
>>>>>> ——
>>>>>> Subject: Re: Maven
>>>>>> From: Lachlan Deck <lachlan.d...@gmail.com>
>>>>>> 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-8a7e-4c5d-836b-3c82faba6...@mac.com>
>>>>>> ——
>>>>>>
>>>>>> Maven uses the relevant plugin for your <packaging /> to determine where
>>>>>> things live. So if you’re using `woapplication` or `woframework` (I
>>>>>> think the options are) as your packaging type, then you’ll need the
>>>>>> relevant plugin in your build section which I think from memory is the
>>>>>> womaven-lifecycle-plugin.
>>>>>>
>>>>>> This has been the case for some years, though I’m not familiar with the
>>>>>> current state of things. Have you tried a basic hello world app
>>>>>> following the wiki guides for maven?
>>>>>>
>>>>>> cheers,
>>>>>> Lachlan
>>>>>>
>>>>>>
>>>>>>> On 22 Mar 2016, at 4:01 AM, Hugi Thordarson <h...@karlmenn.is> wrote:
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> - hugi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On 21. mar. 2016, at 16:26, Hugi Thordarson <h...@karlmenn.is> wrote:
>>>>>>>>
>>>>>>>> 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 dev machine, these xml-files are copied to the
>>>>>>>> jar file as I would expect. But when I run the very same build on my
>>>>>>>> jenkins server, the files just get copied to
>>>>>>>> MyApp.woa/Contents/Resources, but not into the jar file.
>>>>>>>>
>>>>>>>> Any ideas?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> - hugi
>>>>>>>>
>>>>>>>> // Hugi Thordarson
>>>>>>>> // http://www.loftfar.is/
>>>>>>>> // s. 895-6688
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is
>>>>>>>>
>>>>>>>> This email sent to h...@karlmenn.is
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/lachlan.deck%40gmail.com
>>>>>>>
>>>>>>> This email sent to lachlan.d...@gmail.com
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
>
> This email sent to rgur...@smarthealth.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
