October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-23309: --------------------------------------- Link: http://download.eclipse.org/m2e-wtp/signed/mavenarchiver/0.17.2/ Version: 0.17.2.201606141937-signed-20160830073346 > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23309: ------------------------------------- [~nickboldt] please use the version from http://download.eclipse.org/m2e-wtp/signed/mavenarchiver/0.17.2/ > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ This can be verified the next time we need to use the scripts, on Nov 24, for the AM3/GA branch & code freeze. > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2, 4.4.2.Final > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23091: ------------------------------- Fix Version/s: 4.4.2.Final > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2, 4.4.2.Final > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23310) Provide IDE meta-files in source code

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23310?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23310: ------------------------------------- I need some more context please. What projects are you trying to import? When importing eclipse plugin projects, as maven projects, you need to have the m2eclipse tycho integration first (see Preference > Maven > Discovery) > Provide IDE meta-files in source code > ------------------------------------- > > Key: JBIDE-23310 > URL: https://issues.jboss.org/browse/JBIDE-23310 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Aurélien Pupier > > it will help other contributors to setup the environment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23207) Maven configuration error whe using maven-jar-plugin and maven-war-plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23207?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23207: ------------------------------------ When available please put the URL of the update site to fetch into devstudio/jbosstools target platform in JBIDE-23309. > Maven configuration error whe using maven-jar-plugin and maven-war-plugin > ------------------------------------------------------------------------- > > Key: JBIDE-23207 > URL: https://issues.jboss.org/browse/JBIDE-23207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Reporter: Josef Kopriva > > Error in project when using maven-jar-plugin and maven-war-plugin. > Example POM file: > {code:java} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>test</groupId> > <artifactId>test</artifactId> > <version>1.0-SNAPSHOT</version> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-jar-plugin</artifactId> > <version>3.0.2</version> > </plugin> > </plugins> > </pluginManagement> > </build> > </project> > {code} > Error: > Description Resource Path Location Type > org.codehaus.plexus.archiver.jar.Manifest.write(java.io.PrintWriter) pom.xml /test line 1 Maven Configuration Problem > Devstudio: > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160920-0457-B6061 > Build date: 20160920-0457 > org.sonatype.m2e.mavenarchiver version: > 0.17.1.201602251832-signed-20160525150658 > This issue is also logged on Github with more information: > https://github.com/tesla/m2eclipse-mavenarchiver/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23309: ------------------------------- Fix Version/s: 4.4.2.AM2 > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23309 at 10/11/16 9:19 AM: -------------------------------------------------------------- [~jkopriva] Please provide URL of the latest version so I know which version you've used/tested/want, and where to get it. [~fbricon] please confirm. was (Author: nickboldt): Please provide URL of the latest version so I know which version you've used/tested/want, and where to get it. > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23309: ------------------------------------ Please provide URL of the latest version so I know which version you've used/tested/want, and where to get it. > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23310) Provide IDE meta-files in source code

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23310?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-23310: ----------------------------------------- Did you choose to import as Maven projects (Right click the project -> Update Maven Configuration)? That usually works for me, maybe an M2Eclipse bug? [~fbricon]? > Provide IDE meta-files in source code > ------------------------------------- > > Key: JBIDE-23310 > URL: https://issues.jboss.org/browse/JBIDE-23310 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Aurélien Pupier > > it will help other contributors to setup the environment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016