Henrique, excellent!
Let's work on this together, using Jira and this list for
communication. My main motivation at this point is JApplication task,
but we can get the entire thing going now, filling in missing tasks
over time.
Here is the initial suggestions:
1. I assume your company is willing to donate to WOProject the
archetype plugin that you've developed. Let's do this via a Jira task
with attachment. This way there'll be a clear record documenting the
initial donation. Then we'll check it in and continue development
using WOProject repo.
2. A groupId of "org.objectstyle.woproject.maven2" makes more sense
than the one I suggested yesterday.
3. SVN folder layout (trying to figure out some logical split between
the tasks that we have ... JApplication looks like a different kind
of animal, so probably still a separate plugin)
woproject/maven2/
pom.xml /* parent pom */
woarchetype/ /* your archetype plugin */
woproject-plugin/ /* core woproject tasks */
japplication-plugin /* JApplication task */
I did not include PBIndex and friends - not sure whether those are
still useful.
Let me know what do you think. I'll start setting up the general
structure today.
Andrus
On Sep 28, 2006, at 9:33 AM, Henrique Prange wrote:
> Hi Ulrich,
>
> I'm a volunteer. I'm very interested in develop a wo-maven-plugin:
>
> http://objectstyle.org/woproject-old/lists/woproject-dev/
> 2006/08/0209.html
> http://objectstyle.org/woproject-old/lists/woproject-dev/
> 2006/08/0167.html
>
> We have already done an initial archetype plug-in with the standard
> layout for a new WO application on my company.
>
> If you want, we'll be glad to collaborate.
>
> Best Regards,
>
> Henrique
>
> Ulrich Köster wrote:
>> Am 27.09.2006 um 22:08 schrieb Andrus Adamchik:
>>> Uli,
>>>
>>> I looked at the existing Maven plugins under woproject/
>>> mavenplugins and it looks like they are for Maven 1.x. Any reason
>>> why not Maven 2, or am I missing something?
>> Maven 2 was not available at the time of writing. It's that
>> simple ;-)
>>>
>>> I started a 2.0 plugin that is a wrapper for JApplication ant
>>> task. So woproject.jar is a dependency. The easiest thing we can
>>> do to avoid changing woproject build scripts is deploy it
>>> manually to http://objectstyle.org/maven2 repo per [1]. Before I
>>> do that, I wanted to run by you the group and artifact names, so
>>> that we have some consistency.
>>>
>>> Core WOProject:
>>>
>>> groupId: org.objectstyle.woproject
>>> artifactId: woproject
>>> version: 1.2-SNAPSHOT [or whatever we choose for the new
>>> release version?]
>> 2.0.0.3***
>>>
>>> Plugin:
>>>
>>> groupId: org.objectstyle.woproject
>>> artifactId: maven-japplication-plugin
>>> version: 1.2-SNAPSHOT [match the core lib version]
>> I'm fine with the ids.
>>>
>>> Also I wonder if we even need separate plugins for individual Ant
>>> tasks in WOProject? Maybe stick them all in the same plugin with
>>> different "goals" - one per Ant task?
>> We could move it in one plugin.
>>>
>>> Thoughts?
>> My list is getting longer and longer. Some volunteers for the
>> maven plugins?
>>>
>>> Andrus
>>>
>>> [1] http://maven.apache.org/guides/mini/guide-3rd-party-jars-
>>> remote.html
>
> --
>
> \o/ Henrique Prange, Moleque de Idéias Educaçăo e Tecnologia Ltda
> | Phone: 55-21-2710-0178 E-mail: hprang..oleque.com.br
> / \ http://www.moleque.com.br
>
This archive was generated by hypermail 2.0.0 : Thu Sep 28 2006 - 10:31:00 EDT