[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16355:
---------------------------------------------
Ah, I missed the multi-version of it. Yeah, thats better for a Final release report.
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186, https://github.com/jbosstools/jbosstools-webservices/pull/106, https://github.com/jbosstools/jbosstools-build-sites/pull/126, https://github.com/jbdevstudio/jbdevstudio-product/pull/125 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186, https://github.com/jbosstools/jbosstools-webservices/pull/106, https://github.com/jbosstools/jbosstools-build-sites/pull/126)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186, https://github.com/jbosstools/jbosstools-webservices/pull/106, https://github.com/jbosstools/jbosstools-build-sites/pull/126 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186, https://github.com/jbosstools/jbosstools-webservices/pull/106)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16355:
------------------------------------
Mine has multiple versions collected into a single report, omits the unneeded block of HTML at the bottom, and includes a page header so you know what version(s) are included. It's the report from which the static HTML snapshots have created for the past few years.
Yours is a single milestone (CR1 only) and doesn't explicitly state for which version of JBT is included in the report.
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16371) Application wizard: provide checkboxes for (per application-type) applicable markers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16371:
-------------------------------------
Summary: Application wizard: provide checkboxes for (per application-type) applicable markers (was: Application wizard: provide toggles for markers)
> Application wizard: provide checkboxes for (per application-type) applicable markers
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16371
> URL: https://issues.jboss.org/browse/JBIDE-16371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
> Attachments: project-page.png
>
>
> Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
> We should offer these markers as toggles in the Application wizard on the project configuration page:
> !progject-page.png!
> In a mail with Max and Burr:
> {quote}
> for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
> {quote}
> When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16372) Can't build forge
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-16372:
--------------------------------------
Summary: Can't build forge
Key: JBIDE-16372
URL: https://issues.jboss.org/browse/JBIDE-16372
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Mickael Istria
Priority: Blocker
Fix For: 4.2.0.Alpha2
When trying to build forge locally or on CI, we can see
{quote}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.4:copy (get-runtime) on project org.jboss.tools.forge2.runtime: Unable to find artifact. Failure to find org.jboss.forge.addon:shell-api:jar:2.0.0.CR1 in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.jboss.forge.addon -DartifactId=shell-api -Dversion=2.0.0.CR1 -Dpackaging=jar -Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the file there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.jboss.forge.addon -DartifactId=shell-api -Dversion=2.0.0.CR1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]
[ERROR]
[ERROR] org.jboss.forge.addon:shell-api:jar:2.0.0.CR1
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
[ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true),
[ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases/, releases=true, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.jboss.tools.forge2.runtime
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16371) Application wizard: provide toggles for markers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16371:
-------------------------------------
Description:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard on the project configuration page:
!progject-page.png!
was:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard
> Application wizard: provide toggles for markers
> -----------------------------------------------
>
> Key: JBIDE-16371
> URL: https://issues.jboss.org/browse/JBIDE-16371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
> Attachments: project-page.png
>
>
> Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
> We should offer these markers as toggles in the Application wizard on the project configuration page:
> !progject-page.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months