Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MooseElement should be removed #562

Closed
seandenigris opened this issue Aug 3, 2015 · 4 comments
Closed

MooseElement should be removed #562

seandenigris opened this issue Aug 3, 2015 · 4 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with ID 562

It is legacy code.

Reported by alexandre.bergel on 2011-03-22 22:44:12
@seandenigris
Copy link
Contributor Author 

Indeed, it should be merged with MooseEntity.

Reported by tudor@tudorgirba.com on 2011-08-03 02:40:59

@seandenigris
Copy link
Contributor Author 

The two classes are merged.
I removed MooseElement from the hierarchy in Moose.
But I keep it, with a deprecated message in the method new.

We have to remove it for the release.

Reported by jannik.laval on 2011-09-23 14:43:17

  • Status changed: Started

@seandenigris
Copy link
Contributor Author 

Good work. 

I removed MooseElement. There is no class that depends on it.

Reported by tudor.girba on 2011-09-23 15:24:29

  • Labels added: Component-MooseCore, Milestone-4.6

@seandenigris
Copy link
Contributor Author 

Also, I just needed to merge the tests as well (always double check if there is no other
commit before committing your changes:))

Reported by tudor.girba on 2011-09-23 15:25:17

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seandenigris