You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ja...@sybase.com on 2006/01/09 17:59:43 UTC

port build to maven2

If no one else is working on this, and there is consensus
that it is a desirable thing to do, I volunteer to port
the build to maven2.

Is there a patch submission mechanism for folks who are
not committers?

-- 
Jack Unrue
junrue@sybase.com


Re: Tuscany JIRA components

Posted by Kevin Williams <ke...@qwest.net>.
Good point.  Eventually there will be different DAS implementations 
available for different back-ends and in different languages.  Since 
this first one is for relational databases it should probably be 
"DAS-RDB-Java"
Thanks,
--Kevin

Jeremy Boynes wrote:

>Kevin Williams wrote:
>  
>
>>Jeremy,
>>Can you create a DAS component?  Actually, we probably need a component
>>for each Tuscany subproject.
>>    
>>
>
>Do we want to reflect C++ and Java in the name? i.e do we want "DAS",
>"DAS - Java", "Java - DAS" or something else?
>
>--
>Jeremy
>
>
>
>  
>



Re: Tuscany JIRA components

Posted by Jeremy Boynes <jb...@apache.org>.
Kevin Williams wrote:
> Jeremy,
> Can you create a DAS component?  Actually, we probably need a component
> for each Tuscany subproject.

Do we want to reflect C++ and Java in the name? i.e do we want "DAS",
"DAS - Java", "Java - DAS" or something else?

--
Jeremy

Tuscany JIRA components

Posted by Kevin Williams <ke...@qwest.net>.
Jeremy,
Can you create a DAS component?  Actually, we probably need a component 
for each Tuscany subproject.
Thanks,
--Kevin


Jeremy Boynes wrote:

>jack.unrue@sybase.com wrote:
>  
>
>>I created a JIRA issue for this. Perhaps someone with the
>>proper permissions could add a new component such as
>>"infrastructure" or whatever you feel is best and then
>>hopefully I can fix up the entry I just created so that
>>it is categorized correctly.
>>
>>    
>>
>
>I added a component "Build System" and updated this issue to that type.
>
>Thanks
>--
>Jeremy
>
>
>
>  
>



Re: port build to maven2

Posted by Jeremy Boynes <jb...@apache.org>.
jack.unrue@sybase.com wrote:
> 
> I created a JIRA issue for this. Perhaps someone with the
> proper permissions could add a new component such as
> "infrastructure" or whatever you feel is best and then
> hopefully I can fix up the entry I just created so that
> it is categorized correctly.
> 

I added a component "Build System" and updated this issue to that type.

Thanks
--
Jeremy

Re: port build to maven2

Posted by ja...@sybase.com.
Jeremy wrote:
> I had a look at starting this over the break and have a
> couple of pom.xml files for the spec projects that may
> be a starting point (attached). If you open a JIRA and
> attach patches (per Dims's mail) I will help apply them.
>
> My +1 for upgrading to M2.

Jeremy, many thanks for those files.

I created a JIRA issue for this. Perhaps someone with the
proper permissions could add a new component such as
"infrastructure" or whatever you feel is best and then
hopefully I can fix up the entry I just created so that
it is categorized correctly.

-- 
Jack Unrue
junrue@sybase.com


Re: port build to maven2

Posted by Jeremy Boynes <jb...@apache.org>.
jack.unrue@sybase.com wrote:
> If no one else is working on this, and there is consensus
> that it is a desirable thing to do, I volunteer to port
> the build to maven2.
>
> Is there a patch submission mechanism for folks who are
> not committers?
>

I had a look at starting this over the break and have a couple of
pom.xml files for the spec projects that may be a starting point
(attached). If you open a JIRA and attach patches (per Dims's mail) I
will help apply them.

My +1 for upgrading to M2.
--
Jeremy


Re: port build to maven2

Posted by Mike Edwards <mi...@gmail.com>.
Jack,

+1 to this suggestion too.

I think Maven2 is far enough along now - and much of the
documentation and help relating to Maven is heavily focussed
on Maven2, so making the switch is necessary in the near future.

Yours,  Mike.

jack.unrue@sybase.com wrote:
> If no one else is working on this, and there is consensus
> that it is a desirable thing to do, I volunteer to port
> the build to maven2.
> 
> Is there a patch submission mechanism for folks who are
> not committers?
> 

Re: port build to maven2

Posted by Davanum Srinivas <da...@gmail.com>.
Usual process is as follows - Open a JIRA bug, run "svn diff" on your
box, zip up the output, upload the zip to JIRA, make sure you grant
the license to ASF (there's a choice when u upload the files).

thanks,
dims

On 1/9/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
> jack.unrue@sybase.com wrote:
> > If no one else is working on this, and there is consensus
> > that it is a desirable thing to do, I volunteer to port
> > the build to maven2.
> >
> > Is there a patch submission mechanism for folks who are
> > not committers?
> >
> >
> Thanks Jack!
>
> We're in the process of establishing the new project layout so this is
> probably the right time to do this. On the other hand we need to make
> sure that Maven 2 is stable enough. I think we can keep both the maven 1
> and 2 builds in place until we get maven 2 working well, and then decide
> when we want to phase out the maven 1 build.
>
> So I'm +1 on this. What do the other people in the group think?
>
> I'm expecting to find an Apache convention / best practices for
> submitting patches. Maybe Ken, Jeremy or Eddie can jump in and describe
> to the group how they've been handling patches on other Apache
> projects?  or point us to a document on the Apache site describing the
> usual process?
>
> --
> Jean-Sebastien Delfino
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

Re: port build to maven2

Posted by Jean-Sebastien Delfino <js...@apache.org>.
jack.unrue@sybase.com wrote:
> If no one else is working on this, and there is consensus
> that it is a desirable thing to do, I volunteer to port
> the build to maven2.
>
> Is there a patch submission mechanism for folks who are
> not committers?
>
>   
Thanks Jack!

We're in the process of establishing the new project layout so this is 
probably the right time to do this. On the other hand we need to make 
sure that Maven 2 is stable enough. I think we can keep both the maven 1 
and 2 builds in place until we get maven 2 working well, and then decide 
when we want to phase out the maven 1 build.

So I'm +1 on this. What do the other people in the group think?

I'm expecting to find an Apache convention / best practices for 
submitting patches. Maybe Ken, Jeremy or Eddie can jump in and describe  
to the group how they've been handling patches on other Apache 
projects?  or point us to a document on the Apache site describing the 
usual process?

-- 
Jean-Sebastien Delfino