Re: [vote] Removing the reactor POM from root of main Aries repo

[Jean-Baptiste Onofré]

+1

It sounds good to me.

Regards
JB

Le 17 déc. 2018 à 22:32, à 22:32, Christian Schneider  
a écrit:
>+1
>
>makes sense. People try to build all and are disappointed when it does
>not
>work.
>I also wonder which modules we might dispose... many have not seen a
>release for years.
>
>Christian
>
>
>Am Mo., 17. Dez. 2018 um 18:07 Uhr schrieb Raymond Auge <
>raymond.a...@liferay.com>:
>
>> Hey all,
>>
>> I'd like to remove the reactor POM from the root of the main Aries
>repo.
>> This is just a source of pain for attracting new contributors who
>don't
>> realize that the Aries repo has evolved to an aggregate of disparate
>> projects.
>>
>> Thoughts?
>> --
>> *Raymond Augé* 
>>  (@rotty3000)
>> Senior Software Architect *Liferay, Inc.* 
>>  (@Liferay)
>> Board Member & EEG Co-Chair, OSGi Alliance 
>> (@OSGiAlliance)
>>
>
>
>--
>--
>Christian Schneider
>http://www.liquid-reality.de
>
>Computer Scientist
>http://www.adobe.com

Re: [vote] Removing the reactor POM from root of main Aries repo

[Raymond Auge]

On Mon, Dec 17, 2018 at 4:32 PM Christian Schneider 
wrote:

> +1
>
> makes sense. People try to build all and are disappointed when it does not
> work.
> I also wonder which modules we might dispose... many have not seen a
> release for years.
>

I agree. I think several could be retired. I'll try to do an audit and
report back.

- Ray


>
> Christian
>
>
> Am Mo., 17. Dez. 2018 um 18:07 Uhr schrieb Raymond Auge <
> raymond.a...@liferay.com>:
>
> > Hey all,
> >
> > I'd like to remove the reactor POM from the root of the main Aries repo.
> > This is just a source of pain for attracting new contributors who don't
> > realize that the Aries repo has evolved to an aggregate of disparate
> > projects.
> >
> > Thoughts?
> > --
> > *Raymond Augé* 
> >  (@rotty3000)
> > Senior Software Architect *Liferay, Inc.* 
> >  (@Liferay)
> > Board Member & EEG Co-Chair, OSGi Alliance 
> > (@OSGiAlliance)
> >
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [vote] Removing the reactor POM from root of main Aries repo

[Christian Schneider]

+1

makes sense. People try to build all and are disappointed when it does not
work.
I also wonder which modules we might dispose... many have not seen a
release for years.

Christian


Am Mo., 17. Dez. 2018 um 18:07 Uhr schrieb Raymond Auge <
raymond.a...@liferay.com>:

> Hey all,
>
> I'd like to remove the reactor POM from the root of the main Aries repo.
> This is just a source of pain for attracting new contributors who don't
> realize that the Aries repo has evolved to an aggregate of disparate
> projects.
>
> Thoughts?
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>


-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: [vote] Removing the reactor POM from root of main Aries repo

[Dominik Przybysz]

+1

pon., 17 gru 2018 o 18:14 David Bosschaert 
napisał(a):

> Hi Ray,
>
> Sounds like a good plan to me.
>
> Best regards,
>
> David
>
> On Mon, 17 Dec 2018 at 17:07, Raymond Auge 
> wrote:
>
> > Hey all,
> >
> > I'd like to remove the reactor POM from the root of the main Aries repo.
> > This is just a source of pain for attracting new contributors who don't
> > realize that the Aries repo has evolved to an aggregate of disparate
> > projects.
> >
> > Thoughts?
> > --
> > *Raymond Augé* 
> >  (@rotty3000)
> > Senior Software Architect *Liferay, Inc.* 
> >  (@Liferay)
> > Board Member & EEG Co-Chair, OSGi Alliance 
> > (@OSGiAlliance)
> >
>


-- 
Pozdrawiam / Regards,
Dominik Przybysz

Re: [vote] Removing the reactor POM from root of main Aries repo

[David Bosschaert]

Hi Ray,

Sounds like a good plan to me.

Best regards,

David

On Mon, 17 Dec 2018 at 17:07, Raymond Auge  wrote:

> Hey all,
>
> I'd like to remove the reactor POM from the root of the main Aries repo.
> This is just a source of pain for attracting new contributors who don't
> realize that the Aries repo has evolved to an aggregate of disparate
> projects.
>
> Thoughts?
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>

[vote] Removing the reactor POM from root of main Aries repo

[Raymond Auge]

Hey all,

I'd like to remove the reactor POM from the root of the main Aries repo.
This is just a source of pain for attracting new contributors who don't
realize that the Aries repo has evolved to an aggregate of disparate
projects.

Thoughts?
-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

[jira] [Closed] (ARIES-1115) Blueprint 1.2.0 ext schema not available at expected deploy location

[Martin Lichtin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARIES-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Lichtin closed ARIES-1115.
-
Resolution: Fixed

Link is now working.

> Blueprint 1.2.0 ext schema not available at expected deploy location
> 
>
> Key: ARIES-1115
> URL: https://issues.apache.org/jira/browse/ARIES-1115
> Project: Aries
>  Issue Type: Bug
>Reporter: Martin Lichtin
>Priority: Major
>
> Version 1.0.0 and 1.1.0 are available at
> http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
> http://aries.apache.org/schemas/blueprint-ext/blueprint-ext-1.1.xsd
> However, version 1.2.0 is not yet deployed. Can this be arranged?
> It's file blueprint-ext-1.2.xsd and should be available via
> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.2.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ARIES-1067) XML schemas not all available online - for example blueprint-cm-1.2.0.xsd

[Martin Lichtin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARIES-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Lichtin closed ARIES-1067.
-
Resolution: Fixed

Links are now working.

> XML schemas not all available online - for example blueprint-cm-1.2.0.xsd
> -
>
> Key: ARIES-1067
> URL: https://issues.apache.org/jira/browse/ARIES-1067
> Project: Aries
>  Issue Type: Improvement
>Reporter: Martin Lichtin
>Priority: Major
>
> Not all blueprint schemas seem available. Missing:
> http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0
> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.2.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)