[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13408:
----------------------------------------
This is still SNAPSHOTs, and parent pom still reference last release. We'll send a mail when parent pom will be changed to use the new SNAPSHOT of TP with a sum up of applied and upcoming changes.
> investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13408
> URL: https://issues.jboss.org/browse/JBIDE-13408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots.
> Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error:
> {quote}
> {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1]
> {code}
> {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
13 years
[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-3628:
--------------------------------------------
Ah didnt realize the data on this- thanks Rob ;)
Thus I went and looked in our 7 alpha what the state is:
max@slowbeard: $ find . -maxdepth 1 -type d | grep *jboss* /Applications/jbdevstudio7alpha1/studio/plugins
grep: org.jboss.ide.eclipse.archives.core_3.4.100.Alpha1-v20130217-1728-B11: Is a directory
grep: org.jboss.ide.eclipse.freemarker_1.3.0.Final-v20130207-2332-B83: Is a directory
grep: org.jboss.tools.common.gef_3.5.0.Alpha1-v20130216-0701-B10: Is a directory
grep: org.jboss.tools.common.model.ui_3.5.0.Alpha1-v20130216-0701-B10: Is a directory
grep: org.jboss.tools.common.model_3.5.0.Alpha1-v20130216-0701-B10: Is a directory
grep: org.jboss.tools.common.projecttemplates_3.5.0.Alpha1-v20130216-0701-B10: Is a directory
grep: org.jboss.tools.forge.runtime.ext_1.2.0.Alpha1-v20130216-0716-B10: Is a directory
grep: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130216-0716-B10: Is a directory
grep: org.jboss.tools.hibernate.ui_3.7.0.Alpha1-v20130216-0715-B7: Is a directory
grep: org.jboss.tools.hibernate4_0_3.7.0.Alpha1-v20130216-0715-B7: Is a directory
grep: org.jboss.tools.jsf.vpe.ajax4jsf_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.facelets_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.jbpm_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.jsf_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.jstl_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.myfaces_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.richfaces_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jsf.vpe.seam_3.5.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.jst.web.kb_3.5.0.Alpha1-v20130211-2005-B3: Is a directory
grep: org.jboss.tools.struts.vpe.struts_3.4.0.Alpha1-v20130214-1356-B6: Is a directory
grep: org.jboss.tools.vpe.docbook_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.html_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.jsp_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.resref_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.spring_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.ui.palette_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe.xulrunner_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.vpe_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
grep: org.jboss.tools.xulrunner.initializer_3.5.0.Alpha1-v20130218-1313-B9: Is a directory
Out of these I believe the following has no reason to be exploded:
org.jboss.ide.eclipse.*
org.jboss.tools.common*
org.jboss.tools.jsf.vpe*
org.jboss.tools.struts.*
org.jboss.tools.vpe*
The xulrunner, hibernate and forge are dirs because of the jar library they contain (would have to be unzipped constantly)
> Plugins should be .jar's not directories for efficiency sake
> ------------------------------------------------------------
>
> Key: JBIDE-3628
> URL: https://issues.jboss.org/browse/JBIDE-3628
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.1.x
>
> Attachments: exception.log
>
>
> 65 of our plugins are bundled exploded instead of a .jar
> Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed.
> What should be fixed:
> 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files
> 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files)
> 3. Some plug-ins contain resources registered in XML catalog
> 4. common.projecttemplates contains resources that is used as template for new projects
> 5. TBD
--
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
13 years
[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13408:
---------------------------------------------
A) if we are having changes to target platform every week something is very wrong :)
B) he can easily use a specific target platform locally - no need to push that into every other build.
C) we don't want to add in things that are obviously wrong to do - i.e. adding jmock and other testing libs to the target platform isn't something that should just be done within few hours; nor is removing jetty and adding a new one, nor is adding/updating zest....
That said i'm fine providing snapshots builds with changes, but just send out the email when the suggested TP changes and which changes are coming - don't move the used TPC by the build up to this immediately.
> investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13408
> URL: https://issues.jboss.org/browse/JBIDE-13408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots.
> Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error:
> {quote}
> {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1]
> {code}
> {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
13 years