New profile in trunk

[djencks]

I couldn't quite figure out what to build to get the tomcat stuff so I  
added a new profile to trunk that we can put the working plugins into

To build...

mvn clean install -Pworking

The list of plugins for this profile is in plugins/pom.xml.  Please  
update it when you get something to build :-)

I think we probably want to add a profile to build our bundleized jars  
as well...

I couldn't get the tomcat plugin to build either, but haven't looked  
too hard at what might be wrong.

thanks
david jencks

[Rick McGuire]

David Jencks wrote:

> I couldn't quite figure out what to build to get the tomcat stuff so I
> added a new profile to trunk that we can put the working plugins into
>
> To build...
>
> mvn clean install -Pworking
>
> The list of plugins for this profile is in plugins/pom.xml.  Please
> update it when you get something to build :-)
>
> I think we probably want to add a profile to build our bundleized jars
> as well...
>
> I couldn't get the tomcat plugin to build either, but haven't looked
> too hard at what might be wrong.

David, is this granular to handle subprojects too?  For example, tomcat
is dependent upon some of the pieces of the system-database plugin, but
I've not put any effort into getting the sysdb-console-jetty piece to
build yet.  There are examples of this scattered around the plugins.

Rick
>
> thanks
> david jencks
>

[Donald Woods-2]

Why not switch the logic and only include the working plugins in the
default builds and move everything else to an "all" profile?

That would allow building framework + Tomcat, but skip all the console
pieces until those are ready....


-Donald


Rick McGuire wrote:

> David Jencks wrote:
>> I couldn't quite figure out what to build to get the tomcat stuff so I
>> added a new profile to trunk that we can put the working plugins into
>>
>> To build...
>>
>> mvn clean install -Pworking
>>
>> The list of plugins for this profile is in plugins/pom.xml.  Please
>> update it when you get something to build :-)
>>
>> I think we probably want to add a profile to build our bundleized jars
>> as well...
>>
>> I couldn't get the tomcat plugin to build either, but haven't looked
>> too hard at what might be wrong.
> David, is this granular to handle subprojects too?  For example, tomcat
> is dependent upon some of the pieces of the system-database plugin, but
> I've not put any effort into getting the sysdb-console-jetty piece to
> build yet.  There are examples of this scattered around the plugins.
>
> Rick
>>
>> thanks
>> david jencks
>>
>
>

[djencks]

I like this better.... changing it.

thanks
david jencks

On Nov 6, 2009, at 10:54 AM, Donald Woods wrote:

> Why not switch the logic and only include the working plugins in the  
> default builds and move everything else to an "all" profile?
>
> That would allow building framework + Tomcat, but skip all the  
> console pieces until those are ready....
>
>
> -Donald
>
>
> Rick McGuire wrote:
>> David Jencks wrote:
>>> I couldn't quite figure out what to build to get the tomcat stuff  
>>> so I added a new profile to trunk that we can put the working  
>>> plugins into
>>>
>>> To build...
>>>
>>> mvn clean install -Pworking
>>>
>>> The list of plugins for this profile is in plugins/pom.xml.  
>>> Please update it when you get something to build :-)
>>>
>>> I think we probably want to add a profile to build our bundleized  
>>> jars as well...
>>>
>>> I couldn't get the tomcat plugin to build either, but haven't  
>>> looked too hard at what might be wrong.
>> David, is this granular to handle subprojects too?  For example,  
>> tomcat is dependent upon some of the pieces of the system-database  
>> plugin, but I've not put any effort into getting the sysdb-console-
>> jetty piece to build yet.  There are examples of this scattered  
>> around the plugins.
>> Rick
>>>
>>> thanks
>>> david jencks
>>>

[djencks]

On Nov 6, 2009, at 10:44 AM, Rick McGuire wrote:

> David Jencks wrote:
>> I couldn't quite figure out what to build to get the tomcat stuff  
>> so I added a new profile to trunk that we can put the working  
>> plugins into
>>
>> To build...
>>
>> mvn clean install -Pworking
>>
>> The list of plugins for this profile is in plugins/pom.xml.  Please  
>> update it when you get something to build :-)
>>
>> I think we probably want to add a profile to build our bundleized  
>> jars as well...
>>
>> I couldn't get the tomcat plugin to build either, but haven't  
>> looked too hard at what might be wrong.
> David, is this granular to handle subprojects too?  For example,  
> tomcat is dependent upon some of the pieces of the system-database  
> plugin, but I've not put any effort into getting the sysdb-console-
> jetty piece to build yet.  There are examples of this scattered  
> around the plugins.

I think this should work fine if we use Donald's idea of commenting  
out the non-building module in the main modules section and having an  
"all" profile that builds everything.

I'll try to get this on the osgi hints wiki page too.

thanks
david jencks

>
> Rick
>>
>> thanks
>> david jencks
>>
>