[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3208:
--------------------------------------
{quote}we need to provide an update site that is a composite of multiple nightly builds, updates/*/snapshots/{quote}
I don't understand why we need that.
{quote}this URL must in fact be a symlink to builds/*/snapshots/ (or builds/<jobname>/) so that the N latest builds can be accessed from a single URL{quote}
A symlink or a composite. My preference going for a composite.
{quote}we must ensure that the cleanup script [1] is amended to perform deletes in these new folders, too.{quote}
Cleaning up stuff isn't high priority and shouldn't be treated as a requirement/blocker for any change.
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> {code}
> download.jboss.org
> <earlyaccess,updates,discovery>/mars
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/mars/stable is a pointer back into updates/mars)
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> and
> {code}
> devstudio.redhat.com
> <earlyaccess,updates,discovery>/9.0
> /snapshots
> /staging
> /development
> /stable (updates/9.0/stable is a pointer back into updates/9.0)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18860:
---------------------------------------------
Also just noticed you are on Windows.
This *could* explain missing updates if the file we are trying to update is somehow locked (which would be a bug) by wildfly - but it does not explain your missing lib files and this should show up in error/server log with info what went wrong.
If there is anyway you can give us a copy of the project or even just its dot-metadata (files/folders starting with ., i.e. .project, .classpath, .settings/* etc.) so we could try and reproduce.
> Publish to Wildfly AS does not update files
> -------------------------------------------
>
> Key: JBIDE-18860
> URL: https://issues.jboss.org/browse/JBIDE-18860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Environment: Windows7 64bit, JDK8u25
> Reporter: Darryl Miles
> Priority: Critical
> Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1
>
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18860:
-------------------------------------
any chance you could reproduce with a sample project?
> Publish to Wildfly AS does not update files
> -------------------------------------------
>
> Key: JBIDE-18860
> URL: https://issues.jboss.org/browse/JBIDE-18860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Environment: Windows7 64bit, JDK8u25
> Reporter: Darryl Miles
> Priority: Critical
> Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1
>
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18860:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.2.2.Final
4.3.0.Alpha1
> Publish to Wildfly AS does not update files
> -------------------------------------------
>
> Key: JBIDE-18860
> URL: https://issues.jboss.org/browse/JBIDE-18860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Environment: Windows7 64bit, JDK8u25
> Reporter: Darryl Miles
> Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1
>
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18860:
----------------------------------------
Priority: Critical (was: Major)
> Publish to Wildfly AS does not update files
> -------------------------------------------
>
> Key: JBIDE-18860
> URL: https://issues.jboss.org/browse/JBIDE-18860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Environment: Windows7 64bit, JDK8u25
> Reporter: Darryl Miles
> Priority: Critical
> Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1
>
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18860:
---------------------------------------------
How is the server setup ? is it a remote server or local running one ?
Anything in the error log ?
Anything in the server log ?
Do you have m2e-wtp installed ? if no, then maven projects won't work properly for sure - they will only be configured for the java part, not the "web" (wtp) part and that is known to cause the issue above ;/
> Publish to Wildfly AS does not update files
> -------------------------------------------
>
> Key: JBIDE-18860
> URL: https://issues.jboss.org/browse/JBIDE-18860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Environment: Windows7 64bit, JDK8u25
> Reporter: Darryl Miles
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files
by Darryl Miles (JIRA)
Darryl Miles created JBIDE-18860:
------------------------------------
Summary: Publish to Wildfly AS does not update files
Key: JBIDE-18860
URL: https://issues.jboss.org/browse/JBIDE-18860
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Final
Environment: Windows7 64bit, JDK8u25
Reporter: Darryl Miles
I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
I have an EAR Maven project published to Wildfly 8.x.
there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory.
If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
Now the file is updated.
I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
The timestamps on the files in this directory appear to be up-to-date at each publish event.
As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months