[JBoss JIRA] Created: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
8:07 a.m.
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
[
https://issues.jboss.org/browse/JBIDE-8828?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-8828.
----------------------------------
Resolution: Duplicate Issue
This issue has been fixed by adding a separate type of a project example. See JBIDE-6214.
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
[
https://issues.jboss.org/browse/JBIDE-8828?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-8828:
-------------------------------------
Well, I was verifying that issue, but I had another problem there and I've completely
forgotten to verify it.
Now, when I download
[booking-mavenized|http://anonsvn.jboss.org/repos/jbosstools/workspace/snj...]
which is listed in [example
site|http://download.jboss.org/jbosstools/examples/project-examples-commu...],
the zip contains .project and .settings files.
I think this example zip (and maybe others) should be fixed too, Isn't it? Or is this
because of backward compatibility with JBT 3.1?
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
[
https://issues.jboss.org/browse/JBIDE-8828?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-8828:
---------------------------------
Release Notes Text: (was:
Now, when I download booking-mavenized
which is listed in example site, the zip contains .project and .settings files.
Now there are several types of project examples. They are the following:
1. zipped Eclipse projects
They are old project examples that have to contain Eclipse artifacts (.project,
.classpath, .settings ...). They are imported using the Eclipse import operation.
The booking-mavenized project example is such a project.
2. pure maven project examples
They are archived Maven projects that don't have to contain Eclipse artifacts and are
imported using the m2eclipse import operation (see JBIDE-6214).
3. project examples based on a maven archetype
These project examples don't require any archive, but just a declaration in the
project examples xml file. A project is created based on a maven archetype. See
JBIDE-7890.
4. project examples based on a git/svn repository
This feature hasn't been implemented yet. See JBIDE-8452.
It would be possible to convert the booking-mavenized project example from the type #1 to
#2, but we wouldn't get any new functionality. Type #2 is useful only for creating
pure maven projects.examples.)
Now, when I download booking-mavenized which is listed in example
site, the zip contains .project and .settings files.
Now there are several types of project examples. They are the following:
1. zipped Eclipse projects
They are old project examples that have to contain Eclipse artifacts (.project,
.classpath, .settings ...). They are imported using the Eclipse import operation.
The booking-mavenized project example is such a project.
2. pure maven project examples
They are archived Maven projects that don't have to contain Eclipse artifacts and are
imported using the m2eclipse import operation (see JBIDE-6214).
3. project examples based on a maven archetype
These project examples don't require any archive, but just a declaration in the
project examples xml file. A project is created based on a maven archetype. See
JBIDE-7890.
4. project examples based on a git/svn repository
This feature hasn't been implemented yet. See JBIDE-8452.
It would be possible to convert the booking-mavenized project example from the type #1 to
#2, but we wouldn't get any new functionality. Type #2 is useful only for creating
pure maven projects.examples.
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
[
https://issues.jboss.org/browse/JBIDE-8828?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-8828.
----------------------------------
Release Notes Text:
Now, when I download booking-mavenized which is listed in example
site, the zip contains .project and .settings files.
Now there are several types of project examples. They are the following:
1. zipped Eclipse projects
They are old project examples that have to contain Eclipse artifacts (.project,
.classpath, .settings ...). They are imported using the Eclipse import operation.
The booking-mavenized project example is such a project.
2. pure maven project examples
They are archived Maven projects that don't have to contain Eclipse artifacts and are
imported using the m2eclipse import operation (see JBIDE-6214).
3. project examples based on a maven archetype
These project examples don't require any archive, but just a declaration in the
project examples xml file. A project is created based on a maven archetype. See
JBIDE-7890.
4. project examples based on a git/svn repository
This feature hasn't been implemented yet. See JBIDE-8452.
It would be possible to convert the booking-mavenized project example from the type #1 to
#2, but we wouldn't get any new functionality. Type #2 is useful only for creating
pure maven projects.examples.
Resolution: Rejected
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8828) Remove .project files and .settings folders from mavenized examples
[
https://issues.jboss.org/browse/JBIDE-8828?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-8828.
-------------------------------
OK, thanks of clarification.
Remove .project files and .settings folders from mavenized examples
-------------------------------------------------------------------
Key: JBIDE-8828
URL: https://issues.jboss.org/browse/JBIDE-8828
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 3.2.1.M1
Reporter: Libor Zoubek
Assignee: Snjezana Peco
Are .settings dirs and .project files needed in example zips(booking-mavenized and
others). Could these be removed? m2e should be able to import our projects using poms
only.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5447
days inactive
5454
days old
jbosstools-issues@lists.jboss.org
5 comments
2 participants
participants (2)
-
Libor Zoubek (JIRA) -
Snjezana Peco (JIRA)