Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Dennis Kieselhorst 
On 2018/03/10 03:04:46, Eduardo B  wrote: 
> I can even see it here:
> http://central.maven.org/maven2/org/apache/myfaces/core/myfaces-api/2.3.0/
> 
> But not sure why I cannot see it here when I do the search:
> https://mvnrepository.com/artifact/org.apache.myfaces.core/myfaces-api

I wouldn't care about it, the first thing matters and that looks correct to me.

Cheers
Dennis

Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Eduardo B 
I can even see it here:
http://central.maven.org/maven2/org/apache/myfaces/core/myfaces-api/2.3.0/

But not sure why I cannot see it here when I do the search:
https://mvnrepository.com/artifact/org.apache.myfaces.core/myfaces-api

On Fri, Mar 9, 2018 at 5:55 PM, Eduardo B  wrote:

> Here are the links in the repo:
>
> From release directory: https://repository.apache.org/
> content/repositories/releases/org/apache/myfaces/core/myfaces-api/2.3.0/
>
> From public directory: https://repository.apache.org/content/
> repositories/public/org/apache/myfaces/core/myfaces-api/2.3.0/
>
> From staging directory: https://repository.apache.org/content/
> repositories/staging/org/apache/myfaces/core/myfaces-api/2.3.0/
>
> Is there something else I need to do in https://repository.apache.org/
> nexus repo?
>
> Eduardo
>
> On Fri, Mar 9, 2018 at 4:45 PM, Eduardo B  wrote:
>
>> Hi,
>>
>> I released the repo in nexus last week. Not sure why it has not been
>> published yet.
>>
>> Eduardo
>>
>> On Fri, Mar 9, 2018 at 4:37 PM, Leonardo Uribe  wrote:
>>
>>> Hi
>>>
>>> That's automatic. Once you have released the repo in nexus, you don't
>>> need to do anything else.
>>>
>>> regards,
>>>
>>> Leonardo Uribe
>>>
>>> 2018-03-09 15:21 GMT-05:00 Eduardo B :
>>>
 Thanks again guys, I've been able to update the MyFaces website with
 JSF 2.3: https://myfaces.apache.org/

 I still have one more/final question hopefully.

 How do we get the jars into maven central?

 For example: https://mvnrepository.com/arti
 fact/org.apache.myfaces.core/myfaces-api
   https://mvnrepository.com/arti
 fact/org.apache.myfaces.core/myfaces-impl

 I only see the beta jars.

 Thanks,
 Eduardo

 On Wed, Mar 7, 2018 at 1:58 PM, Leonardo Uribe 
 wrote:

> Hi
>
> It is the same process as in Tobago. Please take a look at
> myfaces-site pom.xml there are some predefined paths:
>
>   
> ${user.home}/myfaces-site/checkout .mainDirectory>
> ${user.home}/myfaces-site/site t.path>
> 
> \${site.mainDirectory}
> file://${user.home}/myfaces-site/site eploy.url>
>   
>
> In my case there was a folder called /home/lu4242/myfaces-site/checkout
> and other /home/lu4242/myfaces-site/site. site:stage create some
> files in "site" folder, then I just override in checkout and commit.
>
> regards,
>
> Leonardo Uribe
>
> 2018-03-07 12:40 GMT-05:00 Udo Schnurpfeil :
>
>> Hi Eduardo,
>>
>> I've never done this for the core (only Tobago), so I'm not sure
>> about that...
>>
>> The site you can see here: https://myfaces.apache.org/ is synced by
>> some automatic job from this repo:
>>
>>  https://svn.apache.org/repos/asf/myfaces/site/publish/
>>
>> So, you need to
>>
>> 1. checkout the relevant parts from that URL
>>
>> 2. building the site (it seems that you have done it already)
>>
>> 3. syncing this site (from 2.) locally to the checkout (from 1.)
>> using "mvn site:stage"
>>
>> 4. commit it
>>
>> It seems, there is no many entry and no subfolder for 2.3 currently.
>> I assume this must be created.
>>
>>
>> For Tobago these steps are described here:
>>
>> https://myfaces.apache.org/tobago/release-checklist.html (look for
>> "Building the site")
>>
>>
>> Hope that helps
>>
>> Udo
>> Am 06.03.18 um 22:33 schrieb Eduardo B:
>>
>> I went ahead and checked out src from https://svn.apache.org/re
>> pos/asf/myfaces/site/trunk/
>>
>> I have modified some files with new download links, reference to
>> MyFaces 2.3.0, etc. When I tried to do mvn site:deploy I'm getting a
>> connection refused error.
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>> uploading site
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
>> (AbstractDeployMojo.java:478)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>> oy(AbstractDeployMojo.java:332)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>> oyTo(AbstractDeployMojo.java:293)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.exec
>> ute(AbstractDeployMojo.java:172)
>>
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>> o(DefaultBuildPluginManager.java:134)
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.maven.wagon.authent
>> ication.AuthenticationException: Cannot connect. Reason:
>> java.net.ConnectException: Connection refused (Connection

Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Eduardo B 
Here are the links in the repo:

>From release directory:
https://repository.apache.org/content/repositories/releases/org/apache/myfaces/core/myfaces-api/2.3.0/

>From public directory:
https://repository.apache.org/content/repositories/public/org/apache/myfaces/core/myfaces-api/2.3.0/

>From staging directory:
https://repository.apache.org/content/repositories/staging/org/apache/myfaces/core/myfaces-api/2.3.0/

Is there something else I need to do in https://repository.apache.org/
nexus repo?

Eduardo

On Fri, Mar 9, 2018 at 4:45 PM, Eduardo B  wrote:

> Hi,
>
> I released the repo in nexus last week. Not sure why it has not been
> published yet.
>
> Eduardo
>
> On Fri, Mar 9, 2018 at 4:37 PM, Leonardo Uribe  wrote:
>
>> Hi
>>
>> That's automatic. Once you have released the repo in nexus, you don't
>> need to do anything else.
>>
>> regards,
>>
>> Leonardo Uribe
>>
>> 2018-03-09 15:21 GMT-05:00 Eduardo B :
>>
>>> Thanks again guys, I've been able to update the MyFaces website with JSF
>>> 2.3: https://myfaces.apache.org/
>>>
>>> I still have one more/final question hopefully.
>>>
>>> How do we get the jars into maven central?
>>>
>>> For example: https://mvnrepository.com/arti
>>> fact/org.apache.myfaces.core/myfaces-api
>>>   https://mvnrepository.com/arti
>>> fact/org.apache.myfaces.core/myfaces-impl
>>>
>>> I only see the beta jars.
>>>
>>> Thanks,
>>> Eduardo
>>>
>>> On Wed, Mar 7, 2018 at 1:58 PM, Leonardo Uribe  wrote:
>>>
 Hi

 It is the same process as in Tobago. Please take a look at myfaces-site
 pom.xml there are some predefined paths:

   
 ${user.home}/myfaces-site/checkout>>> .mainDirectory>
 ${user.home}/myfaces-site/site
 
 \${site.mainDirectory}
 file://${user.home}/myfaces-site/site>>> eploy.url>
   

 In my case there was a folder called /home/lu4242/myfaces-site/checkout
 and other /home/lu4242/myfaces-site/site. site:stage create some files
 in "site" folder, then I just override in checkout and commit.

 regards,

 Leonardo Uribe

 2018-03-07 12:40 GMT-05:00 Udo Schnurpfeil :

> Hi Eduardo,
>
> I've never done this for the core (only Tobago), so I'm not sure about
> that...
>
> The site you can see here: https://myfaces.apache.org/ is synced by
> some automatic job from this repo:
>
>  https://svn.apache.org/repos/asf/myfaces/site/publish/
>
> So, you need to
>
> 1. checkout the relevant parts from that URL
>
> 2. building the site (it seems that you have done it already)
>
> 3. syncing this site (from 2.) locally to the checkout (from 1.) using
> "mvn site:stage"
>
> 4. commit it
>
> It seems, there is no many entry and no subfolder for 2.3 currently. I
> assume this must be created.
>
>
> For Tobago these steps are described here:
>
> https://myfaces.apache.org/tobago/release-checklist.html (look for
> "Building the site")
>
>
> Hope that helps
>
> Udo
> Am 06.03.18 um 22:33 schrieb Eduardo B:
>
> I went ahead and checked out src from https://svn.apache.org/re
> pos/asf/myfaces/site/trunk/
>
> I have modified some files with new download links, reference to
> MyFaces 2.3.0, etc. When I tried to do mvn site:deploy I'm getting a
> connection refused error.
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
> uploading site
>
> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
> (AbstractDeployMojo.java:478)
>
> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
> oy(AbstractDeployMojo.java:332)
>
> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
> oyTo(AbstractDeployMojo.java:293)
>
> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.exec
> ute(AbstractDeployMojo.java:172)
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
> o(DefaultBuildPluginManager.java:134)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
> oExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.maven.wagon.authent
> ication.AuthenticationException: Cannot connect. Reason:
> java.net.ConnectException: Connection refused (Connection refused)
>
> at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.
> openConnectionInternal(AbstractJschWagon.java:264)
>
> at org.apache.maven.wagon.AbstractWagon.openConnection(Abstract
> Wagon.java:115)
>
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.j
> ava:216)
>
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.j
> ava:152)
>
> at

Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Eduardo B 
Hi,

I released the repo in nexus last week. Not sure why it has not been
published yet.

Eduardo

On Fri, Mar 9, 2018 at 4:37 PM, Leonardo Uribe  wrote:

> Hi
>
> That's automatic. Once you have released the repo in nexus, you don't need
> to do anything else.
>
> regards,
>
> Leonardo Uribe
>
> 2018-03-09 15:21 GMT-05:00 Eduardo B :
>
>> Thanks again guys, I've been able to update the MyFaces website with JSF
>> 2.3: https://myfaces.apache.org/
>>
>> I still have one more/final question hopefully.
>>
>> How do we get the jars into maven central?
>>
>> For example: https://mvnrepository.com/artifact/org.apache.myfaces.core/
>> myfaces-api
>>   https://mvnrepository.com/arti
>> fact/org.apache.myfaces.core/myfaces-impl
>>
>> I only see the beta jars.
>>
>> Thanks,
>> Eduardo
>>
>> On Wed, Mar 7, 2018 at 1:58 PM, Leonardo Uribe  wrote:
>>
>>> Hi
>>>
>>> It is the same process as in Tobago. Please take a look at myfaces-site
>>> pom.xml there are some predefined paths:
>>>
>>>   
>>> ${user.home}/myfaces-site/checkout>> .mainDirectory>
>>> ${user.home}/myfaces-site/site
>>> 
>>> \${site.mainDirectory}
>>> file://${user.home}/myfaces-site/site>> eploy.url>
>>>   
>>>
>>> In my case there was a folder called /home/lu4242/myfaces-site/checkout
>>> and other /home/lu4242/myfaces-site/site. site:stage create some files
>>> in "site" folder, then I just override in checkout and commit.
>>>
>>> regards,
>>>
>>> Leonardo Uribe
>>>
>>> 2018-03-07 12:40 GMT-05:00 Udo Schnurpfeil :
>>>
 Hi Eduardo,

 I've never done this for the core (only Tobago), so I'm not sure about
 that...

 The site you can see here: https://myfaces.apache.org/ is synced by
 some automatic job from this repo:

  https://svn.apache.org/repos/asf/myfaces/site/publish/

 So, you need to

 1. checkout the relevant parts from that URL

 2. building the site (it seems that you have done it already)

 3. syncing this site (from 2.) locally to the checkout (from 1.) using
 "mvn site:stage"

 4. commit it

 It seems, there is no many entry and no subfolder for 2.3 currently. I
 assume this must be created.


 For Tobago these steps are described here:

 https://myfaces.apache.org/tobago/release-checklist.html (look for
 "Building the site")


 Hope that helps

 Udo
 Am 06.03.18 um 22:33 schrieb Eduardo B:

 I went ahead and checked out src from https://svn.apache.org/re
 pos/asf/myfaces/site/trunk/

 I have modified some files with new download links, reference to
 MyFaces 2.3.0, etc. When I tried to do mvn site:deploy I'm getting a
 connection refused error.

 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 uploading site

 at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
 (AbstractDeployMojo.java:478)

 at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
 oy(AbstractDeployMojo.java:332)

 at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
 oyTo(AbstractDeployMojo.java:293)

 at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.exec
 ute(AbstractDeployMojo.java:172)

 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
 o(DefaultBuildPluginManager.java:134)

 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
 oExecutor.java:207)

 ... 20 more

 Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
 Cannot connect. Reason: java.net.ConnectException: Connection refused
 (Connection refused)

 at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.
 openConnectionInternal(AbstractJschWagon.java:264)

 at org.apache.maven.wagon.AbstractWagon.openConnection(Abstract
 Wagon.java:115)

 at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:216)

 at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:152)

 at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
 (AbstractDeployMojo.java:428)

 ... 25 more


 Maybe I'm missing some kind of permission in the server?

 Regards,
 Eduardo

 On Tue, Mar 6, 2018 at 2:23 PM, Eduardo B  wrote:

> Thanks a lot for all the help so far.
>
> I have distributed the assembly files already. I'm in the final step
> which is the site deployment.
>
> I know I have to run mvn site:site and mvn site:deploy but where do I
> run those commands from?
>
> Is it from
> 1) https://svn.apache.org/repos/asf/myfaces/site/trunk/
>
> or
> 2) https://svn.apache.org/repos/asf/myfaces/core/tags/myface
> s-core-module-2.3.0/
>
> Also I

Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Leonardo Uribe 
Hi

That's automatic. Once you have released the repo in nexus, you don't need
to do anything else.

regards,

Leonardo Uribe

2018-03-09 15:21 GMT-05:00 Eduardo B :

> Thanks again guys, I've been able to update the MyFaces website with JSF
> 2.3: https://myfaces.apache.org/
>
> I still have one more/final question hopefully.
>
> How do we get the jars into maven central?
>
> For example: https://mvnrepository.com/artifact/org.apache.myfaces.
> core/myfaces-api
>   https://mvnrepository.com/
> artifact/org.apache.myfaces.core/myfaces-impl
>
> I only see the beta jars.
>
> Thanks,
> Eduardo
>
> On Wed, Mar 7, 2018 at 1:58 PM, Leonardo Uribe  wrote:
>
>> Hi
>>
>> It is the same process as in Tobago. Please take a look at myfaces-site
>> pom.xml there are some predefined paths:
>>
>>   
>> ${user.home}/myfaces-site/checkout> .mainDirectory>
>> ${user.home}/myfaces-site/site
>> 
>> \${site.mainDirectory}
>> file://${user.home}/myfaces-site/site> eploy.url>
>>   
>>
>> In my case there was a folder called /home/lu4242/myfaces-site/checkout
>> and other /home/lu4242/myfaces-site/site. site:stage create some files
>> in "site" folder, then I just override in checkout and commit.
>>
>> regards,
>>
>> Leonardo Uribe
>>
>> 2018-03-07 12:40 GMT-05:00 Udo Schnurpfeil :
>>
>>> Hi Eduardo,
>>>
>>> I've never done this for the core (only Tobago), so I'm not sure about
>>> that...
>>>
>>> The site you can see here: https://myfaces.apache.org/ is synced by
>>> some automatic job from this repo:
>>>
>>>  https://svn.apache.org/repos/asf/myfaces/site/publish/
>>>
>>> So, you need to
>>>
>>> 1. checkout the relevant parts from that URL
>>>
>>> 2. building the site (it seems that you have done it already)
>>>
>>> 3. syncing this site (from 2.) locally to the checkout (from 1.) using
>>> "mvn site:stage"
>>>
>>> 4. commit it
>>>
>>> It seems, there is no many entry and no subfolder for 2.3 currently. I
>>> assume this must be created.
>>>
>>>
>>> For Tobago these steps are described here:
>>>
>>> https://myfaces.apache.org/tobago/release-checklist.html (look for
>>> "Building the site")
>>>
>>>
>>> Hope that helps
>>>
>>> Udo
>>> Am 06.03.18 um 22:33 schrieb Eduardo B:
>>>
>>> I went ahead and checked out src from https://svn.apache.org/re
>>> pos/asf/myfaces/site/trunk/
>>>
>>> I have modified some files with new download links, reference to MyFaces
>>> 2.3.0, etc. When I tried to do mvn site:deploy I'm getting a connection
>>> refused error.
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>>> uploading site
>>>
>>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
>>> (AbstractDeployMojo.java:478)
>>>
>>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>>> oy(AbstractDeployMojo.java:332)
>>>
>>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>>> oyTo(AbstractDeployMojo.java:293)
>>>
>>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.exec
>>> ute(AbstractDeployMojo.java:172)
>>>
>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>>> o(DefaultBuildPluginManager.java:134)
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
>>> Cannot connect. Reason: java.net.ConnectException: Connection refused
>>> (Connection refused)
>>>
>>> at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.
>>> openConnectionInternal(AbstractJschWagon.java:264)
>>>
>>> at org.apache.maven.wagon.AbstractWagon.openConnection(Abstract
>>> Wagon.java:115)
>>>
>>> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:216)
>>>
>>> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:152)
>>>
>>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
>>> (AbstractDeployMojo.java:428)
>>>
>>> ... 25 more
>>>
>>>
>>> Maybe I'm missing some kind of permission in the server?
>>>
>>> Regards,
>>> Eduardo
>>>
>>> On Tue, Mar 6, 2018 at 2:23 PM, Eduardo B  wrote:
>>>
 Thanks a lot for all the help so far.

 I have distributed the assembly files already. I'm in the final step
 which is the site deployment.

 I know I have to run mvn site:site and mvn site:deploy but where do I
 run those commands from?

 Is it from
 1) https://svn.apache.org/repos/asf/myfaces/site/trunk/

 or
 2) https://svn.apache.org/repos/asf/myfaces/core/tags/myface
 s-core-module-2.3.0/

 Also I know I have to do some modifications like the download links,
 etc. But how do I create de core23 site? Is it automatically created when
 the commands mentioned about are executed?

 Thanks again,
 Eduardo

 On Mon, Mar 5, 2018 at 5:50 PM, Udo Schnurpfeil 
 wrote:

> Hi Eduardo,
>

Re: Questions about MyFaces 2.3.0 release

2018-03-09 Thread Eduardo B 
Thanks again guys, I've been able to update the MyFaces website with JSF
2.3: https://myfaces.apache.org/

I still have one more/final question hopefully.

How do we get the jars into maven central?

For example:
https://mvnrepository.com/artifact/org.apache.myfaces.core/myfaces-api

https://mvnrepository.com/artifact/org.apache.myfaces.core/myfaces-impl

I only see the beta jars.

Thanks,
Eduardo

On Wed, Mar 7, 2018 at 1:58 PM, Leonardo Uribe  wrote:

> Hi
>
> It is the same process as in Tobago. Please take a look at myfaces-site
> pom.xml there are some predefined paths:
>
>   
> ${user.home}/myfaces-site/checkout site.mainDirectory>
> ${user.home}/myfaces-site/site
> 
> \${site.mainDirectory}
> file://${user.home}/myfaces-site/site
>   
>
> In my case there was a folder called /home/lu4242/myfaces-site/checkout
> and other /home/lu4242/myfaces-site/site. site:stage create some files in
> "site" folder, then I just override in checkout and commit.
>
> regards,
>
> Leonardo Uribe
>
> 2018-03-07 12:40 GMT-05:00 Udo Schnurpfeil :
>
>> Hi Eduardo,
>>
>> I've never done this for the core (only Tobago), so I'm not sure about
>> that...
>>
>> The site you can see here: https://myfaces.apache.org/ is synced by some
>> automatic job from this repo:
>>
>>  https://svn.apache.org/repos/asf/myfaces/site/publish/
>>
>> So, you need to
>>
>> 1. checkout the relevant parts from that URL
>>
>> 2. building the site (it seems that you have done it already)
>>
>> 3. syncing this site (from 2.) locally to the checkout (from 1.) using
>> "mvn site:stage"
>>
>> 4. commit it
>>
>> It seems, there is no many entry and no subfolder for 2.3 currently. I
>> assume this must be created.
>>
>>
>> For Tobago these steps are described here:
>>
>> https://myfaces.apache.org/tobago/release-checklist.html (look for
>> "Building the site")
>>
>>
>> Hope that helps
>>
>> Udo
>> Am 06.03.18 um 22:33 schrieb Eduardo B:
>>
>> I went ahead and checked out src from https://svn.apache.org/re
>> pos/asf/myfaces/site/trunk/
>>
>> I have modified some files with new download links, reference to MyFaces
>> 2.3.0, etc. When I tried to do mvn site:deploy I'm getting a connection
>> refused error.
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>> uploading site
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
>> (AbstractDeployMojo.java:478)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>> oy(AbstractDeployMojo.java:332)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.depl
>> oyTo(AbstractDeployMojo.java:293)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.exec
>> ute(AbstractDeployMojo.java:172)
>>
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>> o(DefaultBuildPluginManager.java:134)
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
>> Cannot connect. Reason: java.net.ConnectException: Connection refused
>> (Connection refused)
>>
>> at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.
>> openConnectionInternal(AbstractJschWagon.java:264)
>>
>> at org.apache.maven.wagon.AbstractWagon.openConnection(Abstract
>> Wagon.java:115)
>>
>> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:216)
>>
>> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:152)
>>
>> at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.push
>> (AbstractDeployMojo.java:428)
>>
>> ... 25 more
>>
>>
>> Maybe I'm missing some kind of permission in the server?
>>
>> Regards,
>> Eduardo
>>
>> On Tue, Mar 6, 2018 at 2:23 PM, Eduardo B  wrote:
>>
>>> Thanks a lot for all the help so far.
>>>
>>> I have distributed the assembly files already. I'm in the final step
>>> which is the site deployment.
>>>
>>> I know I have to run mvn site:site and mvn site:deploy but where do I
>>> run those commands from?
>>>
>>> Is it from
>>> 1) https://svn.apache.org/repos/asf/myfaces/site/trunk/
>>>
>>> or
>>> 2) https://svn.apache.org/repos/asf/myfaces/core/tags/myface
>>> s-core-module-2.3.0/
>>>
>>> Also I know I have to do some modifications like the download links,
>>> etc. But how do I create de core23 site? Is it automatically created when
>>> the commands mentioned about are executed?
>>>
>>> Thanks again,
>>> Eduardo
>>>
>>> On Mon, Mar 5, 2018 at 5:50 PM, Udo Schnurpfeil 
>>> wrote:
>>>
 Hi Eduardo,

 I'm using this description for the releases of Tobago, which might be
 quite similar:

 http://myfaces.apache.org/tobago/release-checklist.html

 For the distribution I use this Script (which is linked on the page
 obove). It loads the artefacts from the maven repo (you may also want to
 use your local artifacts, alliteratively. Than it checks the hashes

[jira] [Created] (TOBAGO-1876) Toggle-Button Example

2018-03-09 Thread Guido Dubois (JIRA) 
Guido Dubois created TOBAGO-1876:


 Summary: Toggle-Button Example
 Key: TOBAGO-1876
 URL: https://issues.apache.org/jira/browse/TOBAGO-1876
 Project: MyFaces Tobago
  Issue Type: Wish
  Components: Core
Affects Versions: 4.1.0
Reporter: Guido Dubois


How to define a toggle-button? Is it possible to define a toggle button in 
Bootstrap style?

Like this:





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

[jira] [Created] (TOBAGO-1875) Collapsible Section AJAX-Style doesn't work in /

2018-03-09 Thread Guido Dubois (JIRA) 
Guido Dubois created TOBAGO-1875:


 Summary: Collapsible Section AJAX-Style doesn't work in 
/
 Key: TOBAGO-1875
 URL: https://issues.apache.org/jira/browse/TOBAGO-1875
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 4.1.0
Reporter: Guido Dubois


Exists a way for  to get the row numbers like in  to define







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

[jira] [Resolved] (TOBAGO-1874) Optimize and cleanup theme building

2018-03-09 Thread Udo Schnurpfeil (JIRA) 

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

Udo Schnurpfeil resolved TOBAGO-1874.
-
Resolution: Fixed

> Optimize and cleanup theme building
> ---
>
> Key: TOBAGO-1874
> URL: https://issues.apache.org/jira/browse/TOBAGO-1874
> Project: MyFaces Tobago
>  Issue Type: Task
>  Components: Build
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.2.0
>
>
> * better performance with parallel execution
>  * after call of profile rebuild-theme should no 2nd build be necessary
>  * bootstrap.min.min.css in standard-theme
>  * clean up pom.xml files



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

[jira] [Resolved] (TOBAGO-1868) Update release process: remove MD5 support

2018-03-09 Thread Udo Schnurpfeil (JIRA) 

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

Udo Schnurpfeil resolved TOBAGO-1868.
-
Resolution: Fixed

> Update release process: remove MD5 support
> --
>
> Key: TOBAGO-1868
> URL: https://issues.apache.org/jira/browse/TOBAGO-1868
> Project: MyFaces Tobago
>  Issue Type: Task
>  Components: Build
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Major
> Fix For: 4.2.0
>
>
> The rules on the Apache pages has been changed:
>  [http://www.apache.org/dev/release-distribution#sigs-and-sums]
> {panel:title=Point 4}
> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).
> {panel}
> I think the current todo for us is, to remove the md5 links from the webpage. 
> The md5 files may reside on the servers, there is no matter with them.
> (I wish, maven and the maven repo would use sha256/512 instead of md5/sha1 
> for the internal checks.)



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

[jira] [Commented] (TOBAGO-1868) Update release process: remove MD5 support

2018-03-09 Thread Udo Schnurpfeil (JIRA) 

[ 
https://issues.apache.org/jira/browse/TOBAGO-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392862#comment-16392862
 ] 

Udo Schnurpfeil commented on TOBAGO-1868:
-

The change in apache pom 19 is only for pgp.

> Update release process: remove MD5 support
> --
>
> Key: TOBAGO-1868
> URL: https://issues.apache.org/jira/browse/TOBAGO-1868
> Project: MyFaces Tobago
>  Issue Type: Task
>  Components: Build
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Major
> Fix For: 4.2.0
>
>
> The rules on the Apache pages has been changed:
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> {panel:title=Point 4}
> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).
> {panel}



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

[jira] [Commented] (TOBAGO-1872) Restart with theme "charlotteville"

2018-03-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/TOBAGO-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392808#comment-16392808
 ] 

Hudson commented on TOBAGO-1872:


SUCCESS: Integrated in Jenkins build Tobago Trunk #1335 (See 
[https://builds.apache.org/job/Tobago%20Trunk/1335/])
TOBAGO-1872: Restart with theme "charlotteville" (lofwyr: rev 
83e978509c4efad086bc45dd1236039446210175)
* (edit) tobago-theme/tobago-theme-charlotteville/src/main/scss/_custom.scss
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.css.map
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.css
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.min.css.map


> Restart with theme "charlotteville"
> ---
>
> Key: TOBAGO-1872
> URL: https://issues.apache.org/jira/browse/TOBAGO-1872
> Project: MyFaces Tobago
>  Issue Type: Task
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Minor
>
> Setup the theme charlotteville to use with Tobago 4.



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

[jira] [Commented] (TOBAGO-1874) Optimize and cleanup theme building

2018-03-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/TOBAGO-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392784#comment-16392784
 ] 

Hudson commented on TOBAGO-1874:


SUCCESS: Integrated in Jenkins build Tobago Trunk #1334 (See 
[https://builds.apache.org/job/Tobago%20Trunk/1334/])
TOBAGO-1874: Optimize and cleanup theme building (lofwyr: rev 
1b7ed1ff1cddb5782a80753ff44f3bfbeb3c3f1c)
* (edit) tobago-theme/tobago-theme-standard/rebuild-theme.txt
* (edit) tobago-theme/tobago-theme-roxborough/pom.xml
* (edit) 
tobago-theme/tobago-theme-roxborough/src/main/resources/META-INF/resources/tobago/roxborough/tobago-bootstrap/_version/css/bootstrap.min.css.map
* (edit) tobago-theme/tobago-theme-roxborough/rebuild-theme.txt
* (edit) tobago-theme/tobago-theme-speyside/pom.xml
* (edit) 
tobago-theme/tobago-theme-scarborough/src/main/resources/META-INF/resources/tobago/scarborough/tobago-bootstrap/_version/css/bootstrap.css.map
* (edit) 
tobago-theme/tobago-theme-roxborough/src/main/resources/META-INF/resources/tobago/roxborough/tobago-bootstrap/_version/css/bootstrap.css
* (edit) tobago-theme/tobago-theme-scarborough/rebuild-theme.txt
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/css/bootstrap.min.css.map
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/css/bootstrap.css
* (edit) 
tobago-theme/tobago-theme-scarborough/src/main/resources/META-INF/resources/tobago/scarborough/tobago-bootstrap/_version/css/bootstrap.min.css.map
* (edit) tobago-theme/tobago-theme-charlotteville/rebuild-theme.txt
* (edit) 
tobago-theme/tobago-theme-speyside/src/main/resources/META-INF/resources/tobago/speyside/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/css/bootstrap.css.map
* (edit) 
tobago-theme/tobago-theme-roxborough/src/main/resources/META-INF/resources/tobago/roxborough/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.css
* (edit) 
tobago-theme/tobago-theme-speyside/src/main/resources/META-INF/resources/tobago/speyside/tobago-bootstrap/_version/css/bootstrap.min.css.map
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-scarborough/src/main/resources/META-INF/resources/tobago/scarborough/tobago-bootstrap/_version/css/bootstrap.css
* (edit) tobago-theme/tobago-theme-scarborough/pom.xml
* (edit) tobago-theme/tobago-theme-standard/pom.xml
* (edit) 
tobago-theme/tobago-theme-speyside/src/main/resources/META-INF/resources/tobago/speyside/tobago-bootstrap/_version/css/bootstrap.css
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.css.map
* (edit) tobago-theme/tobago-theme-speyside/rebuild-theme.txt
* (edit) 
tobago-theme/tobago-theme-scarborough/src/main/resources/META-INF/resources/tobago/scarborough/tobago-bootstrap/_version/css/bootstrap.min.css
* (edit) 
tobago-theme/tobago-theme-speyside/src/main/resources/META-INF/resources/tobago/speyside/tobago-bootstrap/_version/css/bootstrap.css.map
* (edit) 
tobago-theme/tobago-theme-charlotteville/src/main/resources/META-INF/resources/tobago/charlotteville/tobago-bootstrap/_version/css/bootstrap.min.css.map
* (edit) tobago-theme/tobago-theme-charlotteville/pom.xml
* (edit) tobago-theme/pom.xml
* (edit) 
tobago-theme/tobago-theme-roxborough/src/main/resources/META-INF/resources/tobago/roxborough/tobago-bootstrap/_version/css/bootstrap.css.map


> Optimize and cleanup theme building
> ---
>
> Key: TOBAGO-1874
> URL: https://issues.apache.org/jira/browse/TOBAGO-1874
> Project: MyFaces Tobago
>  Issue Type: Task
>  Components: Build
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.2.0
>
>
> * better performance with parallel execution
>  * after call of profile rebuild-theme should no 2nd build be necessary
>  * bootstrap.min.min.css in standard-theme
>  * clean up pom.xml files



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

[jira] [Created] (TOBAGO-1874) Optimize and cleanup theme building

2018-03-09 Thread Udo Schnurpfeil (JIRA) 
Udo Schnurpfeil created TOBAGO-1874:
---

 Summary: Optimize and cleanup theme building
 Key: TOBAGO-1874
 URL: https://issues.apache.org/jira/browse/TOBAGO-1874
 Project: MyFaces Tobago
  Issue Type: Task
  Components: Build
Reporter: Udo Schnurpfeil
Assignee: Udo Schnurpfeil


* better performance with parallel execution
 * after call of profile rebuild-theme should no 2nd build be necessary
 * bootstrap.min.min.css in standard-theme
 * clean up pom.xml files



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